DEV Community


Discussion on: Time to stop using REST...

aghost7 profile image
Jonathan Boudreau

I would also include to graphql cons:

  • Caching is more difficult. Especially for edge.
  • Not as much tooling for implementing microservices. You'll need to roll your own gateway.
  • Monitoring endpoints is going to require a custom solution afaik, since graphql doesn't respect status codes.

I'd also add that OpenAPI supports type checking for REST. There are several code generators just like Graphql for multiple languages.