State of @Defer and @Stream
summary
New GraphQL response format for @defer and @stream ships as a GraphQL JS alpha and is used with Relay at FirstDibs to return multiple payloads: initial payload plus pending/incremental/completed arrays that carry an ID, path and label, and a global hasNext flag. Stream adds an initialCount for list bootstrapping; servers may inline or batch deferred groups to avoid duplicated execution. Non‑nullable errors cancel the deferred fragment; async iterables allow incremental list delivery.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 4:40Problem defer stream solves
- 14:14Response format evolution
- 21:44Batching and performance
- 26:03Error handling in defer stream
- 27:48Feedback and next steps
- 28:17Q&A session
related talks
32mLower Latency With Streaming GraphQL
13m@Defer All the Slow Things
12mHow @Defer and @Stream Will Improve GraphQL Caching
21mStreaming HTTP and GraphQL
25mQuery Now, Render Later: Leveraging @defer for Efficient Data Delivery
25mWhat's next for GraphQL?
35mSemi Concurrent Deduplicated Incremental Delivery
32mGraphQL Future