Panel: The Composite Schemas Working G...
summary
A new Composite Schemas spec defines how federated subgraphs compose into one executable GraphQL supergraph, staying backwards compatible with Apollo Federation while adding explicit lookup directive and require directive semantics, preserved key contracts, and a compile‑time satisfiability check that rejects schemas that cannot be executed. Multiple MIT open‑source implementations exist or are being extended (Hot Chocolate, GraphQL Hive composition, Apollo router), a shared compatibility suite and test corpus guide validation, and the working group coordinates composition, query planning and execution rules.
AI-written summary · about
chapters (11)
- 0:00Introduction to panel
- 1:26Composite vs GraphQL working groups
- 3:58Goals of composite schemas
- 8:38Federation experience in audience
- 8:58Key concepts in new spec
- 13:57Open-source implementations
- 18:12Apollo Federation compatibility
- 22:05Timeline and formalization
- 24:57Satisfiability in schema composition
- 26:47Human challenges in adoption
- 31:46How to contribute
related talks
47mThe State of GraphQL Federation
50mDistributed GraphQL APIs: Breaking Down Monoliths & Unlocking Agility for Dev Teams
13mLightning Talk: Schema Composition Without Federation
08mGraphQL: everything you want in one query
30mGraphQL Fusion Rethinking Distributed GraphQL
56mDistributed GraphQL APIs
48mApollo Federation: Connecting GraphQL Microservices
51mWhy GraphQL is Perfect for Microservices