Connecting Apache Flink and the Pravega Stream Store
summary
Pravega is a stream storage that stores unbounded streams by splitting them into mutable segments that can auto-scaling segments through split and merge and persist data using Apache BookKeeper for low latency and a configurable tier two (HDFS NFS extended S3). Connectors implement a source that uses the Pravega reader group and controller to produce aligned checkpoints with Flink and a sink that uses Pravega transactions to guarantee exactly-once semantics. Integration is implemented and demonstrated, with scaling signals and HA uses under development.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:38What is Stream
- 4:05Processing Streams
- 7:40Pravega
- 15:45Segment Manipulation
- 16:35API Semantics
- 17:40EventDriven API
- 18:54Operation semantics
- 21:14Writers crashing
- 24:27State synchronizer
- 27:53Checkpoints
- 29:43Takeaways
- 31:53Stephan Ewen
- 37:53Writing to Pravega
- 39:13How the transactions work
- 41:21Example
- 44:37Next steps
related talks
51mStream Processing Smackdown: Kafka Streams vs. Apache Flink
42mStream Processing with Apache Flink
32mKeynote: Apache Flink - Completing Cloudera’s End to End Streaming Platform
30mFlink + Pulsar: The Path To Unified Batch and Streaming
42mStreamhouse Architecture with Flink and Paimon
40mThe Seven Deadly Sins of Streaming
25mTips and Tricks for Developing Streaming and Table Connectors
01h 01mApache Fluss: A Streaming Storage for Real-Time Lakehouse
