News for hackers. Stuff that matters.
Re:Migrating to GraphQL: A Practical Assessment by jayd16 on Friday July 05, 2019 @04:03AM (#20360703)
Well this is the conflict. If its just a way to batch dependent queries there are things like capnproto that do that too.

Ideally though, you don't use dependent fetches and you have a bespoke endpoint that collapses the dependent operations possibly as tight as a single join query. If this is the case you're trying to solve, then why shouldn't we strive for something like a declarative query language?

Re:Migrating to GraphQL: A Practical Assessment by acjohnson55 on Friday July 05, 2019 @11:24AM (#20363214)
I haven't looked at capnproto recently, but just because it solves a similar problem doesn't mean there's no room for a different system.

The bespoke endpoint thing is a big part of what GraphQL avoids. It gives you something explorable, but as a team, you can decide how comprehensive you want it to be. If you have a monolithic database, you can use SQL to explore it, but GraphQL often sits in front of a service layer, which connects to my next point.

GraphQL's mutations often map to entire processes, which might change a data store, like a DML SQL operation, but also have other sorts of effects.