Managed federation overview
Apollo provides free managed federation support for graphs that use Apollo Federation.
With managed federation, your subgraphs each publish their schemas to the Apollo, which verifies that they successfully compose into a federated schema.
On composition success, Studio updates your graph's latest configuration, which is available at a special endpoint (called the uplink) that your gateway regularly polls for updates:
Managed federation helps your organization safely validate, coordinate, deploy, and monitor changes to your graph. It provides:
You can modify subgraph schemas (and even add or remove entire subgraphs) without needing to modify or redeploy your gateway. Your gateway is the point of entry to your entire graph, and it should maximize its uptime.
Whenever your gateway obtains an updated configuration from Apollo, it knows that the updated set of subgraph schemas will compose, because the configuration includes the composed supergraph schema.
The gateway also knows that your subgraphs are prepared to handle operations against the updated set of schemas. This is because your subgraphs should register their updated schemas as part of their deployment, meaning they're definitely running by the time the gateway is aware of the configuration change.
And whenever a subgraph accidentally pushes a schema change that doesn't compose, Apollo continues to provide the most recent valid configuration to your gateway.
By using a configuration manager that's external to your gateway, you help ensure the safety of certain schema changes. For example, if you want to migrate a type or field from one subgraph's schema to another, you can perform this migration safely only if you externalize your configuration.
Ready to try it out? Continue to Setup.
Managed federation is strongly recommended for all production environments. For non-production environments (such as local development), it can be helpful instead to manually compose the supergraph schema.