Managing State in Apache Flink
summary
Shows how Flink stores operator state as state snapshots to distributed filesystem using checkpoint barriers, and contrasts JVM-heap vs eager vs lazy serialization with RocksDB doing on-access (lazy) deserialization. Recommends avoiding Kryo for persistent state and using Avro/Thrift or custom serializers, explains how to register state early (open lifecycle) instead of lazily, and documents serializer upgrade hooks that allow restoring savepoints only when the new serializer is compatible.
AI-written summary · about
chapters (5)
related talks
28mRundown of Flink's Checkpoints
42mApache Flink Worst Practices
42mInterview and AMA with the creators of Stateful Functions
42mApache Flink Worst Practices
24mStateful Functions: Flexible like a Microservice, Consistent like a Monolith
51mStream Processing Smackdown: Kafka Streams vs. Apache Flink
38mDeploying Stateful FaaS on Streaming Dataflows
38mPolyglot Actor Model on Flink Stateful Functions
