Stream Processing Smackdown: Kafka Streams vs. Apache Flink
summary
Direct comparison of Kafka Streams and Flink with live-coded examples shows how each handles state, fault tolerance, and scaling: Kafka Streams uses a RocksDB-backed state store and consumer-group partitioning with optional standby replicas for faster recoveries; Flink runs jobs on a clustered JobManager/TaskManager model with incremental checkpoints and watermark-driven windows. Example pipeline computes flight delays using a 15-minute sliding window with a one-minute advance and demonstrates exactly-once semantics end-to-end when enabled.
AI-written summary · about
chapters (12)
- 0:00Stream processing comparison
- 2:50Stream processing basics
- 8:04Kafka scalability
- 13:09Kafka Streams architecture
- 16:40Kafka Streams demo
- 20:53Flink architecture
- 24:24Flink processing example
- 29:23State management comparison
- 32:10Scalability differences
- 37:29Time and window ops
- 41:06Exactly-once semantics
- 46:07Kafka Streams vs Flink
related talks
41mBeyond the Hype: When Apache Flink Solves Real Problems
38mApache Flink: A Very Quick Guide
27mNavigating Streaming Infrastructure
43mA Data Streaming Architecture with Apache Flink #bbuzz
49mscale.bythebay.io: Stephan Ewen, Apache Flink and the Next Wave of Stream Processing Applications
40mRobust Stream Processing with Apache Flink
39mEvaluating Streaming Framework Performance for a Large-Scale...
46mFlink SQL in 2020: Time to show off!
