Stream design workspace / Reading notes
Consumer recovery and replay
A replay should be controlled, inspectable and safe.
Persist progress at a boundary
Record the consumer position after a coherent unit of work. Understand the failure window between applying a result and acknowledging the event.
Make repeated work safe
Use a stable operation key or state transition check for side effects. Duplicate suppression must have a defined scope and retention period.
Isolate the replay
Choose an explicit range and destination before replaying historical data. Prevent unintended messages, external writes or duplicated notifications during recovery tests.