/ Measuring the Cost of a GraphQL Query

Description

Developers tend to centralise the fragments definitions and use them in each query where the entity is used, even if just a subset of the attributes is necessary. Unlike rest, the client needs to be more careful on query optimization because the server must process the client's query and create a tailored response. If the client's query is not optimized, it can lead to the server having to process more data than is necessary, resulting in slower response times. mercurius-explain is a simple and lightweight Mercurius plugin that records how many times a GraphQL resolver is invoked and how long it took to retrieve the data, which helps to keep track of performance changes during development and to troubleshoot possible bottlenecks.

Session 🗣 Intermediate ⭐⭐ Track: Native Languages (Rust, Go lang, C++, C#, .Net, ...)