marten-aggregates

Design event-sourced aggregates with Marten by using sealed record shapes for state, static Apply methods for event handling, and the decider pattern to separate state transitions from command processing.

The decider pattern for event sourcing in Marten separates command handling from state evolution by using static Apply methods on sealed record aggregates, ensuring immutable state transitions within the CritterCab architecture.

Yes, Marten handles the event sourcing storage while Wolverine manages command handling and routing for the event-sourced aggregates, together providing the full CritterCab ecosystem infrastructure.

Structure Marten aggregate events and state by defining the aggregate as a sealed record, applying events through static methods, and managing stream identity to maintain proper event sourcing conventions.

You need event-sourced aggregates in a .NET application when you require an immutable audit log of state changes, utilizing Marten for event storage and Wolverine for decider pattern command processing.

Sealed records are used for Marten event-sourced aggregates to enforce immutability and provide concise value equality, which aligns with the static Apply method conventions and state evolution handling.