ecotone-aggregate

Domain aggregates in Ecotone are modeled by annotating classes with #[Aggregate] or #[EventSourcingAggregate], defining an #[Identifier], and adding static factory methods alongside command handlers to manage state and business workflows.

State-stored aggregates use the #[Aggregate] attribute to persist current state directly, while event-sourced aggregates use #[EventSourcingAggregate] and #[EventSourcingHandler] to rebuild state by replaying domain events.

You map identifiers using the #[Identifier] attribute, optionally supporting composite keys, and wire command handlers using #[CommandHandler] to route specific commands to the correct aggregate instance for state mutation or event generation.

Yes, you can use event sourcing with command handlers by combining #[EventSourcingAggregate], #[CommandHandler], and #[EventSourcingHandler] attributes to handle commands, produce events, and rebuild aggregate state from those events.

The best way to set up aggregate creation and repository access is to use static factory methods annotated with #[CommandHandler] for creation and wire repository access to integrate the aggregate into Ecotone's event-driven workflows.

Use event-sourced aggregates when you need to rebuild state by replaying domain events for auditability, and use state-stored aggregates when you only need to persist the current state directly without event history.