Ask HN: When should I use GraphQL

Post by satvikpendem » Tue, May 28, 2024, 10:11 PM UTC

I_am_tiberius wrote: post #10

satvikpendem wrote: post #5

I wrote another comment the other day ( https://news.ycombinator.com/item?id=37125685 ) about how GraphQL has true typing unlike bolted on solutions to REST, and that most people use GraphQL incorrectly then complain about how they're running into problems with N+1 and all that. Basically, the way Facebook originally designed it was in combination with Relay and its graph query optimizing compiler that can stitch you…

Doesn't the fragment (property selection) feature of graphql only solve the frontend network load part? I mean, I doubt anyone creates an SQL query based on the graphql query properties, right? That means the network load between backend and db server is consistent, independent from which fields are selected via graphql.

Post by bnchrch » Wed, May 29, 2024, 4:49 PM UTC

bnchrch wrote: post #12

At a quick fly over its useful in situations where: - You value typing - You have many relations and interrelations - You have multiple clients with different needs - Your org has a distinct divide between backend and frontend - You need to stitch together data from many different sources (N microservices powering 1 api) Ive had a lot of success with GraphQL and think the idea of providing an API schema instead of an…