Product
Pricing

THE SUPERGRAPH

A new, powerful composition engine for your business and teams.

Explore the stack

REQUEST A DEMO

Tools for collaboration, observability, federation, and more.

See how we can help

GraphOS

The supergraph platform. Build, operate and evolve the supergraph.

Apollo Client

The world’s leading GraphQL client for React, iOS, and Kotlin.

Apollo Server

A TypeScript GraphQL Server for Express, Koa, Lambda, and more.

DEVELOPERS

Docs
GraphQL Tutorials
DevHub
Blog
Community
Events
YouTube

FEATURED EVENTS

GraphQL Summit
[Webinar On-Demand] 10 Best Practices for Schema Governance

Discover the supergraph for your industry.

Delivering rapid success on projects with world-class GraphOS and GraphQL expertise.

Explore tech talks, workshops, product updates & more.

Learn how to build and scale your graph.

Learn how Apollo's solutions and expertise can help you deliver innovation with a unified graph.

Learn how Apollo is transforming the way industry leaders build apps.

Your hub for up-to-date information on Apollo’s security, reliability, and policies.

ABOUT US

Leadership
Careers
Open Positions
Our Team
Partners

SUPPORT

Contact Sales
Get Help
Apollo Help Center
Terms of Service
Privacy Policy
Contact Sales
Create Account

E-Book

Discover your path to a supergraph

Learn how experienced GraphQL champions have migrated their platforms from REST, monoliths, and multiple GraphQL APIs to a federated graph


What You'll Learn

How to adopt GraphQL incrementally and prove value from the beginning

Best practices for migrating to a federated graph from a monolith or multiple GraphQL APIs

How to plan for questions about duplication and type ownership when moving to a single federated graph

Migrations may be perpetual, but they don’t have to be painful

With each new technological advancement in our industry, engineers face an often daunting task of migrating from the current to the new. Today, the rate of innovation in the frontend and backend is reshaping the API tier and keeping organizations in a state of perpetual migration.

For many organizations facing a GraphQL migration, they likely started out with organic pockets of adoption throughout the company. Over time, their GraphQL monoliths or multiple GraphQL APIs faced an inflection point where duplicative efforts or scaling maintenance start to overwhelm the team.

When this happens, teams need to rethink their GraphQL architecture to find a solution that allows them to move quickly, increase their autonomy, and still ensure they can safely deploy changes. The solution? A federated Supergraph.

© 2023 Apollo Graph Inc.

Github icontwitter iconspectrum iconyoutube icon

Company