Migrate Apollo Federation 1.0 Supergraphs to Apollo Federation 2.0
Josh Lambert
We’re announcing an important update: starting with the 1.60 release of Apollo GraphOS Router and Apollo Router Core coming in the next few weeks, Apollo Federation 1.0 supergraphs will no longer be supported. This update accompanies the introduction of a new native query planner in these Apollo Router versions, marking a significant advancement in our technology. Upgrading to Apollo Federation 2.0 is essential to leverage these improvements fully, and as Federation and Apollo Router are mission-critical infrastructure for your API workloads, we are here to guide you through every step of this transition to confidently operating your GraphQL platform.
Understanding the importance of upgrading
The next Apollo Router versions, 1.60 and beyond, include a new native query planner with significant performance enhancements. Our extensive testing of over 620 million operations showed a median 10x improvement in query planning time, a 2.9x reduction in CPU utilization, and a 2.2x reduction in memory consumption. Designed specifically for Federation 2.0 supergraphs, this new query planner simplifies maintenance and enhances security by eliminating dependencies, including the need for a JavaScript execution engine within the Apollo Router process.
Timeline and planning
Federation 1.0 supergraphs have been marked as deprecated in our GraphOS Studio UI and users have not been able to create them since Q3 2023. With the upcoming new Apollo Router versions, support for Federation 1.0 supergraphs will end across all Apollo products, including Apollo Gateway. We strongly recommend you upgrade to Apollo Router and Federation 2.0 to ensure continued compatibility with our latest innovations.
If you are still operating your GraphQL deployment without having yet migrated to Federation 2.0, upgrading to the new query planner in Apollo Router 1.60 and beyond will introduce a breaking change.
Migration to Federation 2.0 is simple and focuses on the composition layer, without requiring changes to existing subgraphs in most cases. You only need to compose a supergraph with Federation 2.0 and typically your subgraphs can continue using Federation 1.0 until they need 2.0 features. Our migration guide details how you can update just your Federation composition step to compile a compatible supergraph.
Available resources and ongoing support
We recognize that transitioning from Federation 1.0 to Federation 2.0 is a significant step for some of our users. This decision reflects our commitment to eliminating the complexities of outdated technology and ensuring our offerings meet the evolving needs of modern API infrastructures. We are dedicated to transparent communication and improving our deprecation processes to help maintain the robustness, efficiency, and security of your systems.
Apollo values your partnership and trust as we continue to innovate. We are here to support you through this transition to keep your API infrastructure powerful and future-proof. For additional support, please visit our Apollo Community or, for GraphOS users, contact our Technical Support team at support@apollographql.com.
