Stream Processing at Lyft with Flink and Beam
summary
Lyft runs real-time pipelines using Apache Flink as the runner and is adopting Apache Beam for Python portability, operating 50+ Flink jobs processing tens of millions of records per second on EC2 (Kubernetes work in progress). Bootstrapping reads historic S3 data plus live Kinesis, creates a checkpoint snapshot, then restarts at lower parallelism; a large fraud job (60 days of events) bootstraps in about four hours. A custom bounded priority queue plus a global watermark (ZooKeeper) prevents partition skew and reduces checkpoint/backpressure failures.
AI-written summary · about
chapters (8)
- 0:00Introduction to Lyft streaming
- 3:27Batch vs stream processing
- 5:14Stream processing concepts
- 10:30Apache Flink at Lyft
- 13:21Apache Beam for Python support
- 14:06Bootstrapping stream jobs
- 19:51Source queue challenges
- 25:54Q&A session
related talks
40mLarge-scale near-real-time (NRT) data analytics platform empowered by Apache Flink
19mBuilding Stateful Streaming Pipelines
34mBeaming Flink to the Cloud @ Netflix
33mFlink and Beam: Current State & Roadmap
36mData processing at Spotify - Why portability matters
30mBuild and run streaming applications with Apache Flink and Amazon Kinesis Data Analytics
20mScale By The Bay 2019: Sharanya Santhanam & Shiv Toolsidass
40mFrom concept to production; the fastest way to develop & deploy Apache Flink jobs
