Event Sourcing in .NET
Event Sourcing in one line Store every state change as an event in an append-only log; rebuild state by replaying events and serve reads from projections. When to use Event Sourcing You need a full audit/history of changes (who did what, when). Complex domain invariants benefit from explicit events and replay. You want temporal queries (state as of time T) or easy rebuilds of new read models. Distributed workflows where event streams are the source of truth. You already embrace CQRS and projections (read models). When not to use it ...