Consider a query that requests posts together with their authors. A naive implementation might fetch all posts first and then execute a database lookup from the author resolver for every post.

With 50 posts, this can become 51 database operations. With 1,000 posts, it can become 1,001 operations.

The important lesson is that GraphQL itself is not causing the database problem. The problem comes from independently resolving related data without batching.