The State of GraphQL Federation
summary
A new composite schema spec defines concrete mechanics: a lookup model (one-off and choice-based lookups) and per-argument require directive mapping so resolvers receive typed injected data instead of opaque blobs, plus a demoed prototype of variable batching and nested request batching that pushes transparent batching into the transport for out‑of‑order, streamable responses. The spec is on GitHub, already interoperates with defer/stream, and the prototype runs but had demo flakiness due to sleeping containers.
AI-written summary · about
chapters (18)
- 0:00GraphQL Federation intro
- 1:27Core concepts in federation
- 3:14Entities and shared types
- 6:28Runtime model in Apollo Federation
- 8:38GraphQL standardization progress
- 12:16Composite Schema Working Group
- 13:20Identity and lookup in federation
- 14:25Lookup and batching solutions
- 19:01Variable batching demo
- 21:38Request batching efficiency
- 23:46Future-proofing with GraphQL specs
- 24:54Lookup directives syntax
- 27:24Requirements in federated schemas
- 31:21Requirements syntax discussion
- 34:57Context and dynamic data
- 42:09Transport-level batching
- 45:00Syntax standardization
- 46:26Q&A
related talks
33mPanel: The Composite Schemas Working G...
11mKeynote: The State of Distributed GraphQL
33mPanel: The Composite Schemas Working Group
31mDesign Principles of Federated GraphQL
32mSpec Agnostic Executor for Federated GraphQL
30mGraphQL Fusion Rethinking Distributed GraphQL
08mGraphQL: everything you want in one query
06mEscape the GraphQL Monolith