Apache Beam (incubating)
summary
Apache Beam traces Google’s evolution from MapReduce/FlumeJava/MillWheel into a single programming model that unifies batch and streaming, implemented as Java and Python SDKs and runnable on Cloud Dataflow, Flink, Spark or locally. It exposes what/where/when/how for temporal processing: element transforms, event-time windowing, triggers and watermarks, and strategies for late-data refinement, providing exactly-once semantics for correctness. The project is Apache-licensed, donated with 44 unanimous votes, and is production-ready with multiple runners and an active ecosystem.
AI-written summary · about
chapters (8)
- 0:00Introduction to Apache Beam
- 0:34Google's data processing evolution
- 4:49Limitations of batch processing
- 7:25MillWheel and streaming correctness
- 9:51Unified batch and streaming model
- 10:33Programming model pillars
- 14:46Apache Beam project launch
- 17:42Q&A session
related talks
52mApache Beam, a unified model for Big Data processing
41mApache Beam: Unified Data Processing
42mApache Beam: A Unified Model for...
47mApache Beam - what do I gain?
39mApache Beam and Google Cloud DataFlow
24mApache beam and google cloud dataflow
29mApache Beam Making Big Data Portable With gRPC
10mDemocratizing the pipeline with Apache Beam and Dataflow
