> having a centralized log as the defining store for updates/ change events is sometimes called: eventsourcing
To clarify slightly: Event Sourcing isn't just emitting events for others, it means that your system is re-reading its own log to derive current state from past-events.
For performance reasons you try to avoid this with stuff like periodic "snapshots", but the capability of has to be there.
To clarify slightly: Event Sourcing isn't just emitting events for others, it means that your system is re-reading its own log to derive current state from past-events.
For performance reasons you try to avoid this with stuff like periodic "snapshots", but the capability of has to be there.