I\'m new in DDD. I 开发者_StackOverflow社区have a Topic entity and Lesson entity. Topic has many Lessons.
In trying to understand Domain Driven Design I keep returning to a question that I can\'t seem to definitively answer.
I开发者_运维技巧 am confused with when to use domain events and when to use double dispatch. Udi encourages us to use domain events to maintain encapsulation of model and away from anemic design, but
Ive heard a lots that aggregate roots depend on the use case. But what does that mean in coding context ?
While viewing Evans\' project on sample DDD project, I notice that in the Cargo entity, Evans uses tracknumber which is an value object. Why he didn\'t chooses plain string tracknumber instead chooses
I\'ve read in DDD book (Eric Evans) that procedures which require to be used in presentation should be moved to services classes. For instance BankAccountManagementService has ChangeBankAccount, GetBy
Which is a better approach, create child entities first, then pass to the aggregate root to add them, or have the aggregate root create them? For example:
There is two things in my project Advertiser and BonusProgram开发者_运维知识库s. Business rules are -:
My architecture is thus: UI project (MVC), connect开发者_C百科ed to my Domain Service Layer (Business rules etc), connected to a Repo Layer.
I have a domain model (see example below) that has several interfaces that are determined based upon the value of properties within the model itself.While the code below \"works\" it doesn\'t feel rig
加载中,请稍侯......