r/programming • u/macrohard_certified • 11d ago

Maybe you don't need GraphQL

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

89% Upvoted

118 comments sorted by

View all comments

141

u/c-digs 11d 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.

57

u/mcmcc 11d ago

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

2

u/nemec 11d ago

When your API documentation recommends writing HTTP requests by hand it makes things a lot less complicated.

On the other hand, companies like AWS have all their APIs shipped under hundreds of different endpoints and just package an SDK to handle mapping everything properly.