I am building a DDD system and we have all the requirements on paper for the system already set. There is a disagreement on how we go about building our domain model that I need an opinion on.
Similar questions have been asked before but not quite the same (unless I missed it) I want to pass IUserInfo class instance through my Service, Domain , Domain Events, Domain Event Handlers...
I have been reading about Domain Events and have seen codes from Udi\'s implementation(http://www.udidahan.com/2009/06/14/domain-events-salvation/)
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
currently I dont know how to identify an aggregate root. I\'ve got the following classes. - Garage - Organisation
I was wondering how I would handle aggregate roots that contain collections with a lot of entities. Like:
My domain m开发者_如何学运维odel looks like this: class Group { private List<Person> persons;
I have an MVC2 n-tier application (DAL, Domain, Service, MVC web) using a DDD approach (Domain Driven Design),having a Domain Model with repositories. My service layer uses a Request/Response pattern,
Looking for some clarification on working with aggregate roots. If I have a model (a question paper) as follows;
How do we model classic many-to-many relationships with CQRS/DDD? I know that both DDD and CQRS implementations and solutions tend to be domain-specific, so it may be difficult to come up with a gene
加载中,请稍侯......