Event Sourcing in .NET Architectures

Event sourcing stores state as a sequence of events rather than current values.

Key ideas:

1. Every state change is an immutable event.

2. Current state is rebuilt by replaying events.

3. Events form an audit log of all changes.

Event sourcing is often combined with CQRS and messaging in distributed .NET systems.

Architecture impact: Event sourcing increases traceability and flexibility but adds complexity — use it where history and auditability are critical.

Reference:

Microsoft: Event Sourcing Pattern

https://learn.microsoft.com/azure/architecture/patterns/event-sourcing