zoom_in Click to enlarge

GraphQL (Apollo Federation)

▲ ▼

language

description GraphQL (Apollo Federation) Overview

GraphQL itself is a query language and a specification, but its implementation via Apollo Federation represents the pinnacle of API-first design for complex microservices. It allows multiple independent services (subgraphs) to expose their data under a single, unified gateway schema. This solves the 'microservices data stitching' problem elegantly, giving clients precise control over data requirements.

help GraphQL (Apollo Federation) FAQ

What problem does Apollo Federation solve in GraphQL?

Apollo Federation lets multiple teams own separate GraphQL subgraphs while exposing one composed supergraph to clients. It is meant for organizations where a single monolithic GraphQL schema would become a bottleneck.

What are subgraphs and a supergraph in Apollo Federation?

A subgraph is one service's part of the overall GraphQL schema, such as products, users, or payments. The supergraph is the composed schema that Apollo Router or a gateway presents to frontend clients.

Why are entity keys important in Apollo Federation?

Federation uses entity definitions and keys, such as a Product identified by an id, so fields for the same object can be resolved across services. The @key directive is one of the core mechanics that lets subgraphs extend shared entities.

How is Apollo Federation different from old GraphQL schema stitching?

Schema stitching usually joins schemas at the gateway with more manual resolver work. Apollo Federation puts ownership boundaries into the schema contract, then uses composition checks so teams can change subgraphs with fewer surprises.

swap_horiz

Looking for GraphQL (Apollo Federation) alternatives? Compare top competitors ranked & scored

arrow_forward