3 ms·
I think it helps to distinguish between (A) event sourcing and (B) systems that emit events as a coordination and communication mechanism only. In the first ca
by Terr_ 8y ago
I think it helps to distinguish between (A) event sourcing and (B) systems that emit events as a coordination and communication mechanism only.
In the first case, you're able to do those replays but you also have the pain of somehow controlling the evolution of that system over time, as event-definitions and the consuming code behavior changes constantly.
I think the second case has a lot more "easy wins" and is a better fit for most systems that do not require exhaustive auditing. You might keep all of the events around in a durable store, but they're more like hieroglyphics in a museum than a library book that is constantly retranslated.