News for hackers. Stuff that matters.

A comment on We Ditched REST and Went with GraphQL: Here’s Why. Parent comment

Re:We Ditched REST and Went with GraphQL: Here’s Why by alexgrover on Sunday March 19, 2023 @02:29AM (#35216557)
All of those problems and solutions are not unique to either tech choice. You can use OpenApi for documentation, a variety of libraries like React-query for caching, and N+1 issues exist (and are arguably more complicated to solve) in graphql.
[ Parent | on HN ]
Re:We Ditched REST and Went with GraphQL: Here’s Why by eurasiantiger on Sunday March 19, 2023 @07:15AM (#35217873)
N+1 issues do not exist when using a graph datastore which supports GraphQL.
[ Parent | on HN ]
Re:We Ditched REST and Went with GraphQL: Here’s Why by alexgrover on Sunday March 19, 2023 @08:13AM (#35218210)
Many/most people don’t though. Dataloader libraries exist for a reason.
[ Parent | on HN ]
Re:We Ditched REST and Went with GraphQL: Here’s Why by zihotki on Sunday March 19, 2023 @08:29AM (#35218297)
This statement is false. N+1 issues may exist even in that case. It may vary what caused it and what are the options to solve it.
[ Parent | on HN ]
Re:We Ditched REST and Went with GraphQL: Here’s Why by eurasiantiger on Sunday March 19, 2023 @09:18AM (#35218638)
Sure, they will exist if someone intentionally codes them in. But not when fetching data is done in one pass.
[ Parent | on HN ]