Regarding the contract between the domain and repository, I gather it\'s best to avoid an all-encompassing generic IReposi开发者_JS百科tory interface with methods such as Create() and Delete()?Unless,
Where does one draw the line in the complexity of an aggregate? To clarify, if my aggregate has a list of ObjectA which has a list of ObjectB which has a list of ObjectC, should my aggregate be respon
EDIT: Although original question is DB agnostic.. following conversation in comments with OP. The question is slightly more DB specific.
I\'m a novice with domain driven design and learning to apply it in my current project. I hope some of you guys have already walked the path and can help me out.
I have a couple questions regarding the relationship between references between two aggregate roots in a DDD model. Refer to the typical Customer/Order model diagrammed below.
I have don开发者_StackOverflowe a fair bit of analysis and have used a number of tools to capture requirements: user created storyboards, use cases, GUI drawings, GUI prototypes, User stories & sc
I\'m trying to use domain driven design while creating a website that is publicly accessible. One problem I\'m having is trying to figure out what the aggregate roots should be for my model. I have a
I could use some help understanding my domain model a bit and making sure I am approaching the design correctly.
In DDD root of an aggregate is the only reference to retrieve its child objects. Repository of root of an aggregate is responsible for giving the root object reference only. If I need child objects th
In Domain Driven Design (DDD), an Entity always has its own unique identity. In my reading on DDD I have seen statements and examples that seem to mix the concepts of \"unique identity\" between Enti
加载中,请稍侯......