domain-event-conventions

Domain events are named using past-tense verbs combined with nouns, avoiding the 'Event' suffix entirely. This convention ensures clarity and consistency when registering events in Marten event streams for event sourcing.

The canonical type shape for a domain event uses sealed records and value objects. Aggregate ID fields must follow the {AggregateTypeName}Id naming convention to ensure clarity and enforce structural consistency across the service.

Naming collisions between domain and integration events are handled by differentiating their structures: domain events remain slim, while integration events are rich. This distinction prevents conflicts and maintains clear boundaries between internal and external event contracts.

Domain event files should be placed alongside commands and handlers within feature-based directories. This organizational convention groups related logic together, improving discoverability and maintaining consistency across service development.

Enum types must be defined within the service's own namespace and should not be shared across services. This isolation prevents cross-service coupling and ensures that each service maintains control over its own domain event definitions.

All domain events must be registered in Marten event streams to ensure they are properly tracked and stored. This registration step is required for the event sourcing mechanism to function correctly within the service.