Panel: The Composite Schemas Working Group
summary
A new Composite Schemas spec aims to standardize how federated GraphQL composes subgraphs, adding explicit features like a lookup directive plus the existing key and require concepts, nested key support, and input/output mapping so lookups can be planned. Multiple open‑source implementations (Hot Chocolate, Guild tools, Apollo router) evolve in parallel, the spec is developed while servers are built and validated, a satisfiability check guarantees composed schemas are executable, and a public compatibility suite will verify implementations.
AI-written summary · about
chapters (12)
- 0:00Introduction to panel
- 1:26Working group differences
- 5:02Purpose of composite schemas
- 8:38Federation experience in audience
- 8:58Key concepts in spec
- 13:52Open source implementations
- 18:28Apollo Federation compatibility
- 20:14Main pending directives
- 22:19Formalization timeline
- 24:47Satisfiability explained
- 26:57Team collaboration challenges
- 31:58How to collaborate
related talks
47mThe State of GraphQL Federation
50mDistributed GraphQL APIs: Breaking Down Monoliths & Unlocking Agility for Dev Teams
13mLightning Talk: Schema Composition Without Federation
56mDistributed GraphQL APIs
30mGraphQL Fusion Rethinking Distributed GraphQL
08mGraphQL: everything you want in one query
59mBuilding Distributed GraphQL APIs
17mOpen Federation - Open Remote Schema Specifications with Other Specs (OpenAPI, etc)