It’s hard to optimize queries when you don’t know in advance what the query will be. To avoid an explosion of database requests when a GraphQL query fetches nested data, it seems like you would need to analyze the query and create a plan for executing it efficiently. But that’s a lot of work, complex, and prone to mistakes. So how can you provide an API that’s not only flexible, but also performs well? ​