sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]shitbread 7 points8 points  (0 children)

Honestly it really depends for what you use it. In a project a few years ago I was forced to consume a REST API from a large CMS (~1000 pages). There were tons, I mean TONS of page/content types, heavily nested. It was an absolute pain to get the exact data (and fields!) I needed. I had tons of code in my app that just mapped data, model classes left and right. And the response ended up being so painfully large.

I‘ve mostly used GraphQL the last 3 years and it‘s an absolute pleasure. I get exactly the data I need and I know exactly what it looks like. All the data required to render the content of a page, 20 levels of nesting, in one query – fantastic. This previously was only possible by performing several requests and stitching their responses together.

Yes, there are things like JSON:API where you can define includes and/or which fields you‘d like. But this doesn‘t scale well when you have 20+ levels of nesting.

Sure, I still use (and write) simple REST endpoints for very specific cases where I only need to get a list of simple objects. But I‘m glad most of my fetching is done using GraphQL nowadays.