Backward compatibility in Federation 2
Yes. As of 15 November 2022,
@apollo/gateway v0.x is officially deprecated, with end-of-life scheduled for 22 September 2023.
@apollo/gateway v2.x remains fully supported.
Eventually. The process of moving to Federation 2 has three steps:
- Upgrade your gateway to support Federation 2.
- Begin composing your supergraph schema with Federation 2 composition logic.
- Update your individual subgraphs to use Federation 2 features and directives.
Steps 1 and 2 usually require no changes to your subgraph schemas. Schemas that do require changes are schemas that should cause certain composition errors that Federation 1 fails to detect (see below.).
Step 3 does require some changes to your subgraph schemas, described here.
As mentioned above, the following Federation 1 examples should produce composition errors, but they aren't detected. If your subgraph schemas include syntax that matches any of these, you need to update those schemas before moving to Federation 2.
No, not after you convert at least one subgraph schema to a true Federation 2 schema.
Federation 2 provides more flexible composition rules compared to Federation 1. After you modify your subgraph schemas to take advantage of this flexibility, your graph will no longer compose with Federation 1. You need to revert these changes to move back to Federation 1.
Yes. If you want, you can update your gateway's
@apollo/gateway library to its latest
2.x version before you're ready to move your graph to Federation 2.
Your plugins and customizations for
0.x will continue to work as expected in
|Router/Gateway version||Federation 1|
|Apollo Router v1.x||🟢||🟢|