The evolution of the GraphQL Orchestrator powering Intuit Consumer Apps
summary
GraphQL Orchestrator powers Intuit Consumer Apps by composing 54 subgraphs into a unified supergraph serving 150+ clients with 18 REST adapters and S3-backed schema persistence. A Java-based registration library validates schemas at startup, enforces schema rename-on-register to resolve conflicts, and supports declarative REST adapters that map REST flows into GraphQL. Authorization happens by redacting queries before execution to avoid unnecessary network calls. Orchestrator adds about 6 ms overhead and sustains ~5k TPS; core components are open source.
AI-written summary · about
chapters (11)
- 0:00Introduction to orchestrator
- 1:26Evolution of orchestration
- 4:35Challenges with past models
- 8:36Designing the new orchestrator
- 10:54Subgraph registration process
- 13:24Key registration takeaways
- 15:43Schema governance and types
- 17:33Schema composition techniques
- 24:08Authorization and security
- 26:41Rest adapters and summary
- 29:13Open source and Q&A
related talks
22mOrchestrating Microservices with GraphQL
19mThe “Food Court Menu” of APIs: A GraphQL Introduction
19mBringing GraphQL to the Enterprise: When IBM met Apollo
05mInterview
24mI’ve finally seen the light, the future is a graph
16mGraphQL: The Internal Agentic API
26mKeynote: Apollo's Journey with GraphQL: Transforming Enterprise APIs for the Future
26mOrchestrating APIs for LLMs - Agentic Workflows for GraphQL