3 ms·
The comparison is mainly of interest to people who believe in silver bullets. REST is going nowhere, and is a highly appropriate choice for lots of situations -
by ealexhudson 9y ago
The comparison is mainly of interest to people who believe in silver bullets. REST is going nowhere, and is a highly appropriate choice for lots of situations - e.g document-oriented stores.
GraphQL solves a number of different issues and is particularly good on the front end, but the ability to write/update data is more limited.
RPC is still a very valid technology, and suits event architectures very well. It's incredibly flexible, but that means you need to spend more time designing a good API.
Choose the best approach for the problem at hand.
- Blackstone4 9y agoThank you for your response. What do you mean by GraphQL's "the ability to write/update data is more limited"?
- ealexhudson 9y agoYou have to define every mutation you need, whereas with REST it's a bit more generic. I think the two are equivalent, but the more mutations you need, the more complex your GraphQL schema becomes.