Making mistakes with GraphQL and lessons learnt

Click for: original source

Bertrand Dubaut article from presentation given at the Amsterdam Ruby meetup. Real life GraphQL in production implementation, mistakes made, corrections and lessons learnt. System supports multiple clients (mobile and web).

They decided to go with GraphQL to help them to solve problems like: (1) Support multiple clients with different requirements (2) Endpoints becoming overloaded with options (3) Duplicated endpoints (4) Specific client/customer requests leading to single use case endpoints.

And main mistakes?:

  • Poor early schema design
  • Returning classic HTTP error codes with empty responses
  • Choosing a collection pattern early

Article will help you decide if GraphQL can be a good fit for you. The example code is provided in the GitHub repo. Good read!

[Read More]

Tags nosql apis software-architecture