GraphQL Federation v2 is our default frontend-to-backend pattern. Backend services can also use the federated graph for read operations that combine data owned by multiple services.
Production backend consumers must use persisted queries. For synchronous operations owned by one service, use JSON over HTTP through the Internal API Gateway instead.
GraphQL is our platform for communication between frontend and backend systems using federation architecture.
We use GraphQL federation to compose multiple service subgraphs into a single federated graph. Each service owns and publishes its subgraph to a schema registry, enabling teams to independently develop and deploy GraphQL schemas while providing a unified endpoint.
We use Apollo GraphQL Gateway to implement federation. The gateway handles schema composition, query planning, and execution across our distributed architecture.
On the frontend, we use Relay as our GraphQL client. Relay enforces schema conventions that all federated services must follow.
This replaced our legacy Ring Data Fetching approach and is part of our platformization strategy.