4 ms·
GraphQL is such a pain. The SDKs are usually bloated. Debugging is a nightmare. Documentation on those APIs feeling adhoc. Outside of rare use-cases, I feel lik
by jadbox 10mo ago
GraphQL is such a pain. The SDKs are usually bloated. Debugging is a nightmare. Documentation on those APIs feeling adhoc. Outside of rare use-cases, I feel like 99% of the time GraphQL is engineering overkill than a simple resource-based REST interface.
- tacker2000 10mo agoYea, i also dont like GraphQL. Why they needed to replace the good old REST interface, which was working perfectly, I will never understand. The tech team there seems to be making some shortsighted decisions in the last couple of years. Lets see if its going to bite them in the long run...
- 0x3f 10mo agoThe funniest thing about GraphQL is when it's set up to only allow specific whitelisted queries. Incredible.
- no_wizard 10mo agoAutomatic type a client generation that is extremely mature. Even when using OpenAPI it’s not as good GraphQL has validation built in, that’s another big one. For non complex and non-specialized types it validates against the schema quite well. Query caching is dead simple and quite good
- squidsoup 10mo agoRelay (and hence GraphQL) does solve some problems that have no immediate solution with REST - over/under fetching (data masking, fragment colocation in components) and automatic cache normalisation, but they are mostly problems you would only have at scale with disconnected frontend teams working on a product. The typesafety you get from a compiler and an automatically generated schema is nice too.