Absolutely. REST APIs are passive and GraphQL APIs are the vice versa, very active and progressive in nature, GraphQL also comes with a simpler model to process real time data (subscriptions). However, it is relatively hard to scale GraphQL (especially if you had Websocket based subscriptions) while REST can be backed by traditional HTTP proxy.
Ask HN: Were you happy moving your API from REST to GraphQL?
181–182 of 182 posts
Re: Ask HN: Were you happy moving your API from REST to GraphQL?
#182Earlier quoted context omitted.
With a standard REST interface, you have to name all such combinations in advance. Possibly build custom code for each. With GraphQL, you specify them all at once, and are guided towards implementing code that will handle that. (There's no magic in GraphQL, of course, but the conceptualization alone can be useful. And if you're already in some particular ecosystem, they may have some localized magic you can use.) You…
> With a standard REST interface There's no such thing. > you have to name all such combinations in advance. No you don't. > Possibly build custom code for each. As much as any other API.
There is a "standard" REST interface described in the paper on REST. There are a lot of rules/guidelines for a RESTful API but many API's don't follow them and tend to be a mix of REST and JSON RPC.