Evolving Yelp's Streaming at Scale
summary
Yelp runs streaming on Flink with a custom control plane, schema registry and CLIs, and currently operates 50 Flink services across 250 clusters running roughly 2,600 jobs. The platform moves from many homegrown components (custom CDC, DataPipelineMessage, Yelp schematized, session clusters) toward a single SQL client, Flink upgrades, and open formats/registries to enable Streamhouse-style separation of compute and object storage while solving autoscaling, state compatibility, and S3 checkpoint retention.
AI-written summary · about
chapters (10)
- 0:00Introduction to streaming at Yelp
- 1:23Streaming ecosystem overview
- 7:27Early data processing with MapReduce
- 9:12Building data pipeline tools
- 12:02Introducing Stormboard for streaming
- 14:10Transitioning to Apache Flink
- 18:29Expanding platform options
- 23:26Platform challenges and strategies
- 30:34Future plans and open source alignment
- 33:46Q&A session
related talks
21mFlink's application at Didi
30mKubernetes + Operator + PaaSTA = Flink @ Yelp
47mBring Flink to Large Scale Production
43mLeverage the power and simplicity of SQL on Apache Flink
20mBuilding metric platform using Flink for massive scale at Netflix
23mBetter, Faster, Stronger Streaming: Your First Dive into Flink SQL
46mFlink SQL in 2020: Time to show off!
34mBeaming Flink to the Cloud @ Netflix
