3 ms·
I think there are a few GraphQL enthusiasts entering this thread right now, which has its own merits, but can live perfectly next to REST.
by stingraycharles 9y ago
I think there are a few GraphQL enthusiasts entering this thread right now, which has its own merits, but can live perfectly next to REST.
- konschubert 9y agoIn my company we use graphql for getting, and REST for all other operations. Might be an antipattern, but has served us well. We're also using a special flavor of graphql that returns the data as flat dictionaries instead of deeply nested dictionaries. Whether you need that or not of course depends on the client design.