Realtime Content Delivery: Powering dynamic instant experiences on your mobile apps
summary
LinkedIn builds a realtime pub/sub platform using Server-Sent Events over HTTP long-poll with Play + Akka actors, a distributed key‑value subscriber store, and standard pub/sub backends (RabbitMQ/Redis compatible). A single front-end handles 100k connections, end-to-end delivery shows ~75 ms p90 for typing indicators, and the same system powers online/offline presence (green dots) and realtime likes/comments, producing a measurable engagement increase.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:23What is Realtime Content Delivery
- 2:27Polling
- 5:23Requirements
- 8:46HTTP Longpole
- 10:54Event Source
- 13:11WebSockets vs Event Source
- 18:30Delivery
- 22:21Event Sources
- 23:38Performance and Scale
- 24:47Speed
- 26:05Summary
related talks
10mBuilding engaged experiences with real-time applications
18mbuilds a realtime chat app with AWS
45mKeeping it Real(time)
25mMixing data streams at scale
32mReal time customer experience across industries
08mReal-Time Data Systems: Speed, Scale, and Resilience
03mTed Roden interviewed at Web 2.0 Expo New York
14mInterview with