Predicting Hacker News with Beam and TensorFlow
summary
Demonstrates using Apache Beam and Google Cloud Dataflow with Java/Python SDKs to solve stragglers and cost by dynamic work rebalancing (aka liquid sharding), plus cluster autoscaling and in-place streaming updates. Beam adds splittable sources so runners (Flink, Spark, Dataflow) can split backlog, scale from ~10 to hundreds of workers, and reassign slow work without double-processing. Prototypes run in production and Dataflow spins up ephemeral clusters and tears them down automatically.
AI-written summary · about
chapters (10)
- 0:00Introduction and apologies
- 0:35Evolution of distributed data processing
- 2:46Motivation for Dataflow and Beam
- 3:50Challenges in streaming pipelines
- 6:42Handling straggling workers
- 9:55Scaling workers in the cloud
- 13:28Dataflow and Beam summary
- 14:52Open source Beam SDK
- 15:14Beam SDK demo
- 17:25Q&A session
related talks
10mDemocratizing the pipeline with Apache Beam and Dataflow
26mBeam and dataflow: a perfect combination of parallel processing
46mBuilding an Apache Beam streaming runtime in GCP
47mAdvances in Stream Analytics: Apache Beam and Google Cloud Dataflow deep-dive
43mNo shard left behind: Dynamic work rebalancing in Apache Beam
39mApache Beam and Google Cloud DataFlow
47mApache Beam - what do I gain?
52mApache Beam, a unified model for Big Data processing
