This group is for discussion of the domain-driven style of designing software, and the book by Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Business Software. Questions and discussion of the book content is welcome here, as well as sharing of experiences applying DDD, and discussions of the topic in general.
When doing event sourcing, aggregate roots provide all of their state changes to their repository. From the repository, the change events can be persisted and
Jesper, I think you've taken things a bit too far. The command side of things behaves just as any standard ORM app would. No need to use the query side at all
If you're willing to give up have dependencies injected into your domain objects, things can be simplified immensely. No need to use DI or IoC to create your
Perhaps for the nightly import you could look at using events which are then consumed by your domain layer? For example we have a similar situation - data
Are you building an API layer that is meant to be completely self-contained and reused in any context? If so, there are some additional questions that need to