The State of GraphQL Federation
summary
GraphQL Federation becomes a vendor-neutral Composite Schema standard that adds concrete primitives: a new variable batching protocol for batching multiple variable versions, combined request patching to merge downstream requests, and an entities/lookup model replacing the node anti-pattern. The working group (Apollo, ChiliCream, Dgraph) supplies a compliance test suite and gateway benchmarks (constant, burst) that reveal plans yielding either 18 or 5 downstream requests, and independent implementations already include a Java gateway called Fedy and community Python ports.
AI-written summary · about
chapters (5)
- 0:00Introduction and goals
- 3:57Federation specification evolution
- 10:23Batching and request patching
- 13:15Validation and benchmarks
- 16:34Community adoption and next steps
related talks
38mGraphQL Federation in the Wild
26mBest Practices for Federated GraphQL: Lessons from Teya
27mStranger Graphs - Building Federated Workflows with Shared Components
22m8 Years of GraphQL: Unraveling the Trade-Offs
01h 17mSafely Evolve Your (Federated) GraphQL Schema with GraphQL Hive
30mHow to Choose a GraphQL Gateway
23mAn Introduction to GraphQL
30mDeep Learnings Migrating legacy services to Federated GraphQL