The GitHub web hooks (which is basically REST) post a deeply nested json full of nodes (that you “might need”) which I don’t need, and lacking info I do need (ended up having to do another round trip to GQL after receiving the bloated web hook payload)
I have seen suboptimal APIs on both technologies.
If you don’t have control over the API, it doesn’t matter if it uses SQL, so following your logic the issue seems to be that you cannot change the API, not the tech it uses.
The difference is the culture/background/ecosystem around GraphQL, which makes it happen more often. It's the easy path there.
But your problem is mostly because the API is not under your control.
In GraphQL backends it's OK to add special queries adapted for specific UI/UX (I think it's the whole idea behind the BFF - Backend-For-Frontend pattern).
I.e. you can choose between Design-first (data-centric) or Client-first (optimized for rendering on the Client/Front-end) GraphQL schema methodologies.
In the Client-first GraphQL schema you can have queries returning flattened data.
A non-standard approach is to run transformations, i.e. you specify directives how to transform the GraphQL operation responses. This can be for flattening, aggregations, calculating statistics, or joining results of the different queries.
https://www.graphql-mesh.com/docs/getting-started/mesh-trans...
Otherwise hype-following developers think it's a good idea to just go ahead and use them, despite not having the unique needs and resources of neither of those megacorps.
Moral of the ramble, new tech is great – sometimes.
> Moral of the ramble, new tech is great – sometimes.
> https://www.graphql-code-generator.com
You can do this with a boring REST API too. Most frameworks can automatically generate a swagger file, and there is a tool to generate clients from this in lots of different languages.
query {
users {
email: contact.email
}
}GQL also has some affordance for renaming fields (although admittedly nothing like SQL for the client, if you did allow running sql via the client it would be harder to sanitize, so this is a “feature” not a “bug”)
Feels like something that came with a graph database, and people tried to blindly copy it.
Graphql code generator is great though. Absolutely wonderful. Makes it really hard to go back to rest.
For example, rather than having top level "admin contact email" and "business contact email", API designers will have a sub graph of contacts, with label->email. (Note that this is the trivial example, it gets much worse)
Most of the time, I need a flattened version to actually do the work. Now, with SQL, that's not an issue because I can put a query together that flattens/joins as needed. But, with a GraphQL result withs lots of edges and nodes, I can't do that simply. I have to write some bespoke recursive walker to pull the data back up.
I understand I could fix this with the schema, but these aren't my APIs, I'm just a consumer. There doesn't seem to be some universally supported way to do the equivalent of a join.
Or, more simply, the culture around REST/JSON seems to prefer flatter structures, but the GraphQL crowd tends to like more nested structures...even when it's not really needed.
Edit: Also, it's not so simple to make a universal, declarative-driven "flattener", as the nested structures vary pretty wildly in how they are done.