Savepoint
A savepoint is an operator-owned snapshot for controlled restarts and planned changes. Retained checkpoints can also support some changes, subject to compatibility limits.
A savepoint is an operator-owned snapshot for controlled restarts and planned changes. Retained checkpoints can also support some changes, subject to compatibility limits.
Heap state is limited by available memory. Embedded RocksDB supports larger state within available disk capacity, with serialization and storage costs on access.
The choice is rarely about features. It is about the latency you actually need, how much state you will carry, and whether you want a cluster to operate.
Lag, replay, and upgrades are where stateful streaming jobs usually fail. Work through the arithmetic and the procedures that keep restarts and rollouts safe.
A checkpoint restores a job’s state, not the outside world. Trace restart, sink commits, and crash points to see where exactly-once ends.
A watermark is an estimate, not a fact. See how the delay you choose trades result latency against dropped or revised records, and what it costs in state.