Craft GraphQL APIs in Elixir with Absinthe

Chapter 9Tuning Resolution

As your knowledge of GraphQL grows and you start to imagine how your APIs might need to scale and deal with different problems, you’re bound to have questions that go beyond basic field resolvers and middleware.

Resolvers (as we’ve been using them so far in the book) execute one after another, serially. What if we want to have some of them happen concurrently instead? If several fields on the same object need to retrieve the same data, how could we execute those fields together so that we don’t calculate the same value more than once, negatively affecting performance? How do we make decisions by looking at the whole GraphQL document, rather than just field by field, to efficiently execute a query, mutation, or subscription? ...