Lightning Talk: Schema Composition Without Federation
summary
Meta runs hundreds of schema changes per day and replaces a federated supergraph with product-specific subset schemas that build independently using Buck and incremental builds, cutting CI time and blast radius. Composition uses set ops — union, intersect and an exclude operation that flags which product commits block others — and a GAP 33 SDL proposal plus a schema set crate and Relay 21 compiler hooks to make exclusion and enum-value extensions practical.
AI-written summary · about
chapters (8)
- 0:00Introduction to schema composition
- 1:51Federation limitations and issues
- 3:35Breaking changes and CI problems
- 6:27Modular schema subsets approach
- 7:52Benefits of subset schemas
- 9:18Schema set operations explained
- 10:43SDL gaps and future work
- 11:04Q&A session
related talks
33mPanel: The Composite Schemas Working G...
33mPanel: The Composite Schemas Working Group
47mThe State of GraphQL Federation
31mDesign Principles of Federated GraphQL
50mDistributed GraphQL APIs: Breaking Down Monoliths & Unlocking Agility for Dev Teams
30mSo you want to distribute your GraphQL schema?
41mOptimizing Shared Types: How Intuit Streamlined Schema Evolution in a Federated Graph
32mIn-House Schema Registry - The Good the Bad and the Ugly