By now, the hype of GraphQL has surely made its way to your development teamâ€™s watercooler talk, whether in casual conversation, or in serious considerations about building your companyâ€™s next API, but how does one separate the fact from the hype around this new technology?
In some cases, GraphQL is a great solution; for others, it is not. For particular data stores, a GraphQL interface is an asset; for others it brings with it the possibility of enormous (and, perhaps, very unexpected) computational complexity. After cutting many respective teeth on these victories and failures, I thought the best way to move past them (and learn from them) is to organize them, and try to help others on the same path.
This talk will not just be a â€œREST vs GraphQLâ€ cage-match. This talk will walk you through real experiences, born in production environments that relished in the promise of GraphQLâ€™s flexibility, but also paid dearly in pain-points and bottlenecks, so hopefully you can anticipate much of these things yourself and build beautiful Ruby APIs with ease.