ecotone-event-sourcing

To build event-sourced aggregates and read models in Ecotone, you model domain state as a sequence of events using the event store and apply projections via ProjectionV2 and FromStream. This enables state reconstruction, auditability, and scalable reads.

Event versioning in event sourcing is handled safely through upcasting using Revision and NamedEvent attributes. This approach allows you to evolve event schemas over time without breaking existing event streams or requiring data migrations.

You replay events to rebuild a read model projection by leveraging Ecotone's event store and stream-based processing capabilities. This replays the event sequence across multiple streams and deployments to reconstruct the current projection state.

Yes, event sourcing projections can run across multiple streams and deployments using Ecotone's stream-based processing. The framework requires unique projection naming to ensure consistent event processing and read model synchronization across environments.

You need event sourcing when managing complex domain state that requires full auditability and replay capabilities. By storing a sequence of events rather than just current state, you enable state reconstruction and scalable read models built from event streams.

Ecotone projections require unique naming to satisfy stream-based processing requirements across multiple deployments. This ensures events are correctly routed and applied to their intended read models during replay and synchronization.