|
|
|
|
|
|
by CreepGin
3238 days ago
|
|
|
There are still many gaps the developers need to fill in order to use GraphQL in production. But when implemented correctly, one of the practical benefits is that multiple queries from client to server can be merged into one, thus saving bandwidth and improving performance. a full query model of your domain means an explosive quantity of potential strategies piped through a single endpoint.
I agree with this fact. But like you said, it's just trade-offs. I'm sure certain types of projects will benefit more from the pros than cons of GraphQL. But certainly not all projects will do so. |
|
|
Sure, but if we're doing that by dragging the API implementer over every possible permutation of queries, optimizing whatever you could possibly ask for, I'm not convinced this is LESS work than me shipping BTO API requests.
> I'm sure certain types of projects will benefit more from the pros than cons of GraphQL.
My sneaking suspicion is that it's the kind of projects where their data model is small and isolated and doesn't offer much sharing between queries. Which is great when you can get it.