This is a simple enhancement to the existing functionality of replaying events, so it's up to the implementor to either lock the domain from state change during the replay, or do a diff and patch at the end
Design Considerations
Support multiple running application instances
Only one instance should perform the replay, even though all are running and capable
Motivation
Required for performing a large-scale full replay of all events for:
This is a simple enhancement to the existing functionality of replaying events, so it's up to the implementor to either lock the domain from state change during the replay, or do a diff and patch at the end
Design Considerations
Support multiple running application instances
Only one instance should perform the replay, even though all are running and capable
Sequential batching
Events replayed in chronological order, across all batches.
Lifecycle hooks for implementation to control state-change while running
Either events or simple hooks