I have a question on implementing the repository pattern with my data model. I have searched online and looked into a lot of posts but I do not find any answer which clears my doubts. Basically our do
The problem is that I have two aggregate roots The Aggregate roots are Project. NewsArticle. A Project can have a collection of related NewsArticle.
Based on the following definitions from Domain-Driven Design: Tackling Complexity in the Heart of Software,
I\'m currently working a lot with DDD, and I\'m facing a problem when loading/operating on aggregate roots from other aggregate roots.
I have an application in which an Engineer accesses gas wells.He can see a list of wells by choosing any combination of 7 characteristics.The characteristics are company, state, county, basin, branch,
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:
I was wondering if how my presentation layer is structured could be a lead to开发者_开发技巧 design my aggregate roots.
I understand that we should not change children of an aggregate-root directly, but instead they should be performed via methods on the aggregate-root.
I have the need to persist a calculated property with an aggregate root. The calculation is based on child entities. I am using the root to add/remove the children via domain methods, and these method
Can someone please clarify the following; if a have the following model; presentation-->slide-->video where I have identified presentation as the aggregate root, does this mean that if I want to ad
加载中,请稍侯......