Hacker News new | ask | show | jobs
by jschrf 1243 days ago
I think GraphQL goes away in 5-10 years and we can place it next to the whole NoSQL craze and just move on, but that's me.

I've never seen it be anything but accidental complexity, but would love any concrete examples of where it's been worth the effort.

2 comments

From the client perspective, I've always seen the main three benefits (compared to rest) as: avoiding overfetching, avoiding underfetching, and type safety. Ideal case is one query to get exactly what you want, and to know what you're getting.
I love GraphQL, it makes writing typed APIs for multiple clients very easy, since client code can basically be auto generated from the GraphQL schema. More concretely, it forces you to think about your data, unlike NoSQL where you can just chuck a JSON blob of whatever you want.