What's next for GraphQL?
summary
Preview of concrete changes: the spec work focuses on @stream and @defer using multipart HTTP responses to send patches (demo cuts a single POST from ~2s to 340ms by streaming vital assets first, typical runs produce ~20 patches; a nested stream can explode to ~3,000 patches), plus a proposal for fragment modularity so fragments can be reasoned about and tested in isolation, and client‑controlled nullability to mark client error boundaries. Early implementations run in Banana Cake Pop, Hot Chocolate and GraphQL.js; proposals live in the spec repos for review.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:39What's next for GraphQL?
- 10:42Fragment Modularity
- 12:48Reason about Fragments in isolation
- 15:51Client Controlled Nullability
- 16:25Non-Null Propagation
- 17:14Error Boundaries
related talks
21mStreaming HTTP and GraphQL
32mLower Latency With Streaming GraphQL
32mGraphQL Future
12mImprove Application Performance and User Engagement with Advanced GraphQL Features
13m@Defer All the Slow Things
37mGraphQL — A New Look at the API
23mAn Introduction to GraphQL
27mGraphQL: Towards a universal query language