Beyond the Hype: When Apache Flink Solves Real Problems
summary
When Flink becomes essential: event-driven fraud detection, CDC that syncs RDBMS to search in sub-second, and low-latency dashboards where freshness matters; concrete contrasts include Kafka Streams = JVM library, Kafka-native, no SQL, ksqlDB = SQL on Kafka with its own cluster, and Spark Structured Streaming as micro-batch with limited stateful/event-time features. Flink supplies event-time processing, watermarks for out-of-order and late arrivals, exactly-once guarantees, Table API/Flink SQL, Kubernetes deployment, 100+ connectors and fits a streamhouse pattern for real-time OLAP plus longer-term analytical storage.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:04Why streaming matters
- 3:05Core streaming use cases
- 5:11Streaming platform landscape
- 7:26Stream processing entities
- 10:35KSQL DB and streaming databases
- 13:21Streaming databases and patterns
- 16:47Real-time OLAP engines
- 19:13Stream processing frameworks
- 21:07Apache Flink overview
- 23:58Hard problems in streaming
- 26:43Streamhouse architecture
- 31:05Conclusion and takeaways
- 33:49Q&A session
related talks
38mApache Flink: A Very Quick Guide
50mStream Processing Smackdown: Kafka Streams vs. Apache Flink
43mLeverage the power and simplicity of SQL on Apache Flink
49mscale.bythebay.io: Stephan Ewen, Apache Flink and the Next Wave of Stream Processing Applications
42mApache Flink deep-dive #bbuzz
23mBetter, Faster, Stronger Streaming: Your First Dive into Flink SQL
43mA Data Streaming Architecture with Apache Flink #bbuzz
35mApache Flink 2.0: Unified Enterprise Data Processing System and Beyond
