How @Defer and @Stream Will Improve GraphQL Caching
summary
GraphQL edge caching splits a single query into independent cache buckets so cached subfields return immediately while uncached parts are fetched separately, enabling partial query caching and avoiding frontend query-splitting. Real customers see big wins—one reported a 40% cost reduction—and cached product data can reach the client in 50 ms first paint while @defer/@stream delivers remaining fields as a second payload, reducing origin load and preserving a single-request UX.
AI-written summary · about
chapters (6)
- 0:00The importance of caching
- 1:41Challenges with current cache
- 4:11Native caching solutions
- 5:45Leveraging defer and stream
- 6:55Future and conclusions
- 8:06Q&A and closing remarks
related talks
37mCaching Deep Dive: The Ultimate Way To Speed up Your GraphQL API
32mLower Latency With Streaming GraphQL
21mStreaming HTTP and GraphQL
12mImprove Application Performance and User Engagement with Advanced GraphQL Features
25mGraphQL and caching - Why is it so hard, or is it? 
35mState of @Defer and @Stream
24mHow to cache GraphQL queries at the edge
23mHow to Edge Cache GraphQL APIs