Beaming Flink to the Cloud @ Netflix
summary
Netflix runs a Stream Processing as a Service that uses Kafka, Flink and Apache Beam to move and transform live events at massive scale, claiming 700 billion events/day and about 1.3 PB/day of handled data. The system auto-provisions Kafka topics, dashboards and alerts, runs multi-tenant jobs in containers, and achieves four nines availability with migrations that keep the gap under <0.1% data loss.
AI-written summary · about
chapters (7)
- 0:00Netflix event infrastructure
- 3:01Keystone architecture
- 7:13Routing and deployment
- 13:41Transitioning to Flink
- 19:29Titus and Flink integration
- 23:33Performance and enhancements
- 29:32Future directions and QA
related talks
22mNetflix Data Mesh: Composable Data Processing
25mData: Moving with the flow
49mscale.bythebay.io: Stephan Ewen, Apache Flink and the Next Wave of Stream Processing Applications
43mA Data Streaming Architecture with Apache Flink #bbuzz
20mBuilding metric platform using Flink for massive scale at Netflix
35mApache Flink 2.0: Unified Enterprise Data Processing System and Beyond
19mBuilding Stateful Streaming Pipelines
45mApache Flink — Real-Time Data Processing
