Skip to main content

Batched execution

Resolve related GraphQL field work in batches by default, so list-heavy queries do not degrade into per-item backend calls.

Applies to

  • GraphQL servers
  • Execution engines and runtimes
  • Gateways that execute resolvers

Why this should be default

N+1 is one of the most common sources of GraphQL performance failure. Batched execution makes the safe behavior the easiest behavior.

Solves

Implementing patterns