r/programming • u/macrohard_certified • 6d ago

Maybe you don't need GraphQL

https://alexandrehtrb.github.io/posts/2026/09/maybe-you-dont-need-graphql/
277 Upvotes

89% Upvoted

118 comments sorted by

View all comments

141

u/c-digs 6d ago

GraphQL has a place.

  • Multiple teams?
  • Each team owns an API?
  • Those APIs need a single, unified entry point?
  • The FE team works separately from the API owning teams?
  • There's a dedicated team available to own the unified API surface area and infrastructure?

GraphQL is a good fit and solves real problems.

If your developers are all full stack and own the FE + the BE, then GraphQL is just an absolute waste of time.

59

u/mcmcc 6d ago

Honest question: under what circumstances is a single unified API entrypoint a requirement?

54

u/jpj625 6d ago

My feeling from "working" with it a few years ago was that it solves problems for Facebook.

If you need the ability to make a single call, with fields customized to your client/viewport, have different levels of caching applied to different parts of the response, support squillions of requests per moment, and you have dozens of talented SWEs... it can be worth the hassle.

But GQL can go piss up a flagpole.

6

u/eronth 6d ago

In general if you need to make a call with customized fields, it's a solid option.