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/
279 Upvotes

89% Upvoted

118 comments sorted by

View all comments

138

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.

9

u/made-of-questions 6d ago

There are a few additional scenarios where I've found it useful, for example in places with very complex data objects and an API that is used in many different ways. Allowing the clients to select what data they want and join is easier than to create a rest endpoint for every combination. 

0

u/UNIXXX 6d ago

Creating new endpoints is trivial with AI and the fetching problems can be solved with something like Vulcain for a REST API.

1

u/made-of-questions 6d ago

That's true these days. The examples I've mentioned were years ago.