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.
The client does not publish - it sends. The command side of the server is the one which publishes after it has successfully processed a command. The query side
The simplest thing to do is have the service layer which manages the transaction catch the unique constraint exception thrown by the database and not deal with
Doesn't DDD specify that Entities have an Id, but these Id's only have to be unique within the Aggregate where the Id's of AR should be unique within the
I believe that: - An Aggregate cannot hold an object reference to an Entity or AR in an other Aggregate - An Entity or AR can only have a Id reference to an
... For interactions between domain objects in the same bounded context, there's no need to introduce IDs. However, IDs are needed when going across layers of