Should we include domain events in the domain layer?

[danielmackay]

Domain events are a useful concept in DDD to allow us to loosely couple functionality based on events that happen in the system.

• should we have these in the event or domain layer?
• if domain layer, how do we feel about the domain having a dependency on meditation?
• do we need this for all projects? Or just medium-large projects?

[danielmackay]

RE: should we have these in the event or domain layer?

Domain events (if used), MUST be part of the domain layer in order to be consistently triggered

[danielmackay]

RE: if domain layer, how do we feel about the domain having a dependency on meditation?

Ideally, the domain layer should not have any external dependency (as per clean architecture). However, keeping the domain layer clean would result in us having to re-invent the wheel and create our own implementation of domain events publishing and subscription.

We may investigate this in future, but for now we have decided to take a dependency on MediatR in the domain layer.

[danielmackay]

RE: do we need this for all projects? Or just medium-large projects?

No, we don't. In future, we will build a flag into the template so that domain events can be included or not.

For example: dotnet new ssw-ca --use-events