10 ms·
I'd flip that around: depending on which stack/tools I was working in, that would give me a better idea of whether to pick GraphQL or REST. If I'm building a b
by WorldMaker 8y ago
I'd flip that around: depending on which stack/tools I was working in, that would give me a better idea of whether to pick GraphQL or REST.
If I'm building a backend in JS/TS, GraphQL is getting to be just about a no brainer. The tooling for GraphQL, such as Apollo's server products, in JS is fantastic, and can be often highly productive.
On the flipside, if I'm working on .NET (Core) backend, the GraphQL tools are rather lacking still, but a lot of the REST tools are very well refined and capable.
There's a wide spectrum in between of course, too, such as Python which is growing pretty good tools for GraphQL (Graphene I've heard is really good to work with), but also has great REST tools.
Similarly client stack matters too. Again, JS clients for GraphQL are mostly ahead of most other languages. React is great with GraphQL, but some of the other frameworks don't fit the GraphQL model quite as well.
Beyond that, other judgement calls are useful such as development team familiarity and project needs.