7 reasons to use Apache Flink
summary
Shows concrete use: Apache Flink ingests IoT streams from Kafka, keeps state locally (RocksDB), and uses exactly-once checkpoints persisted to S3/HDFS so state and Kafka offsets recover after failures. Uses event-time with watermarks and windowing to reorder and dedupe RFID reads, implements per-asset stateful partitioning and state machines for patient/asset workflows, and powers a production real-time RFID asset-tracking system that handles high throughput and continuous low-latency processing.
AI-written summary · about
chapters (8)
- 0:00Introduction and speakers
- 1:12IoT data properties
- 6:59Apache Flink overview
- 12:43Low latency processing
- 20:22Scalability and state
- 23:16Asset tracking demo
- 28:45Industrial use cases
- 34:29Conclusion and Q&A
related talks
35mEvent Streaming Architecture for Industry 4.0
33mFlink for Everyone: Self-Service Data Analytics with StreamPipes
20mBuilding realtime efficient queries in an IOT platform
17mAlert detection in IoT using broadcast state.
56mTaming IoT Data: Making Sense of Sensors with SQL Streaming
54mApache Wayang: Bringing Big Data to the IoT
31mFun with Sensors
52mDrinking a River of IoT Data with Akka.NET