How GraphQL is Transforming API Innovation at Netflix
summary
Netflix operates a Federated GraphQL platform with Domain Graph Services (DGS), a schema registry and gateway, handling 1B+ requests/day and 500+ active contributors across consumer, studio and internal graphs. Migration yields fewer client round trips and less overfetching but creates schema consistency and learning challenges, so engineering builds Graphup (schema mono‑repo), Graph Doctor linter, Graph Lab sandboxes, schema working groups and usage‑based deprecation and tracing; the platform runs at scale and materially speeds client development while requiring new governance.
AI-written summary · about
chapters (8)
- 0:00Introduction to Netflix APIs
- 3:35Evolution of API Architecture
- 7:24Challenges of the BFF Model
- 12:14Implementing Federated GraphQL
- 19:26Trade-offs in Federated Design
- 25:15Tooling for Collaboration
- 31:38Lessons Learned and Wrap-up
- 34:14Q&A Session
related talks
57mGraphQL at Scale
25mGraph-First Services Using GraphQL
27mHow The Guild is using GraphQL at scale
55mGraphQL - APIs the New Way
10mEvolution of Application Networking Patterns with GraphQL
49mMigrate your APIs to GraphQL: how? and why!
36mThe Graph of Everything - Federated Architecture for Any API Service
47mIntroduction to Graphql