Federated Subscriptions for Real-time Applications
summary
Apollo adds native Federated Subscriptions to GraphOS: the router executes subscription plans across subgraphs, supports multipart subscriptions over HTTP (based on incremental delivery), websockets and a preview HTTP callbacks transport, and implements request deduplication so one router call serves many identical subscribers. Apollo clients (web, iOS, Kotlin) gain support. Benchmarks on a test cluster show 8,000 concurrent connections with mean end‑to‑end latencies around 1–2.25 ms, proving the design performs in practice.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:00Real-time data context
- 3:39Benefits of real-time
- 6:45GraphQL subscription basics
- 10:21Why choose subscriptions
- 12:45Federated challenges
- 16:07Past architectural workarounds
- 20:11Design goals and philosophy
- 23:35Integrated solution features
- 25:24Scalability and architecture
- 27:16Multipart subscriptions
- 30:53Transport and deduplication
- 33:53Performance and closing
related talks
34mGraphQL real-time subscriptions
38mGraphQL Federation in the Wild
37mHigh Stakes, Real Time: How Athenahealth Scaled GraphQL in Clinical Workflows
15mGraphQL Subscriptions in Production Is Easy Isnt It?
32mGraphQL Future
21mSafely Merging Subgraphs in a Distributed World
30mHow to Choose a GraphQL Gateway
25mDetermining the right architecture design when adopting Apollo Fed.