A single GraphQL schema works well for many applications, but very large organizations may have multiple teams and independently deployed services. Maintaining one centralized schema and resolver implementation can become a bottleneck.

Federation allows multiple services to contribute portions of a unified GraphQL API while retaining ownership within individual teams.

The client can query a composed graph without needing to know which backend service owns each field.