GraphQL

This item was not updated in last three versions of the Radar. Should it have appeared in one of the more recent editions, there is a good chance it remains pertinent. However, if the item dates back further, its relevance may have diminished and our current evaluation could vary. Regrettably, our capacity to consistently revisit items from past Radar editions is limited.

Mar 2023

Adopt

GraphQL is a powerful way to expose an API for frontend use. We generally prefer tRPC over GraphQL for frontend-backend integration but still consider GraphQL a valid alternative in cases where tRPC is not a good match.

When tRPC is not a good match we generally prefer GraphQL over REST because it increases flexibility and agility, depending on the context (e.g. external APIs may still require REST for API clients' needs).

Beware of GraphQL misuse however. A mix of GraphQL and REST is also a viable solution.

Sep 2021

Adopt

GraphQL is a powerful way to expose an API for frontend use. We prefer it over REST APIs in most cases because it often increases flexibility and agility, depending on the context (e.g. external APIs may need to use REST for API clients' needs).

Beware of GraphQL misuse however. A mix of GraphQL and REST is also a viable solution.