Supergraph
Success Stories

If you’re a company that’s expecting to build more and scale more, but you still want the confidence that what you’re building is standardized and not slowing you down, then I would recommend you consider an Apollo GraphQL approach.

In all our previous stacks, each individual UI built their own APIs. iOS had one API, Android had another API, TV has a different API, etc. we just couldn’t scale with the business anymore. Unifying those in a single federated GraphQL API was super valuable, and something we couldn't do before.

Bruce Wang

Director of Product Platform Systems team, Netflix

Apollo GraphOS is a key platform for the development team to work softly with GraphQL. It provides a bunch of tools and APIs that allow us to establish a secure development pipeline to compose and deliver new pieces to our supergraph.

Without the supergraph, we’d still be trying to figure out how to build a user journey for the fleet business.

Stephan Lonntorp

Senior Engineering Manager at Volvo Cars

With a supergraph, we could create a single source of truth for definitions of every entity in our data model . . . eliminating a huge amount of maintenance work associated with these disparate graphs. For us, it was worth it.

Mike Byrnes

Principal Software Engineer at Priceline.com

In some cases, teams are almost doubling the speed at which they are releasing features and we are not even close to finishing our modernization journey ... We're just getting faster and faster.

Matt Sexton

Solutions Architect at Booking.com

Centralized monolithic api services are difficult to scale now that we have 1000+ engineers in many time zones. Federation makes it easier to run an automated, centralized API service, which is fantastic. But it really works well with Apollo’s schema management tools because that’s what makes the automation actually possible

Lenny Burdette

Solutions Architect, Apollo GraphQL