I\'m refactoring a project using DDD, but am concerned about not making too many Entities their own Aggregate Root.
I\'m learning domain driven design. I am currently trying to write a simply application in C# designing it using DDD. This application has an aggregate root A which can contain 0..n sub entities B. Th
I was reading a similar question on SO: How update an entity inside Aggregate, but I\'m still not sure how a user interface should interact with entities inside an aggregate.
I am trying to get my head around where the aggrega开发者_开发百科tes roots lie in my entity framework data model so I know what repositories I need to create.
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
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\'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 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
I\'m trying to 开发者_JS百科apply the Aggregate Root pattern to my domain. I\'m using Entity Framework 4 with POCO Entity Generator.
加载中,请稍侯......