Using GraphQL to overcome architecture bottlenecks
GraphQL is a query language that is rapidly gaining wide adoption across the community. It combines type validation with a query and filtering syntax that makes it easy to get up-and-running with a powerful web API in almost no time. Features like running parallel queries or update-all become much easier because they are first-class citizens of GraphQL. Add to that a vibrant community that keeps creating excellent tooling and documentation, it’s clear why GraphQL has become so popular with developers
Every abstraction has a cost, and GraphQL is no exception. The added complexity and a new schema format to parse and execute mean new performance bottlenecks. In addition to performance issues, the wrong use of GraphQL can lead to architectural bottlenecks. Instead of viewing this as a problem, I took this as a challenge.
As a Technical Director at NearForm, Matteo Collina consults for some of the top brands of the world. Matteo is a member of the Node.js Technical Steering Committee focusing on streams, diagnostics and http. He is also the author of Node.js MQTT Broker, Mosca, the fast logger Pino and of the Fastify web framework.
Recorded March 26th 2020 | Work From Home Conf Organised by James Snell – Head of NearForm Research In partnership with NearForm & GitHub. More details here.
Need GraphQL experts for your next project? Contact us today to see how we can help!