In DDD you should never let your entities enter an invalid state. That being said, how do you handle the validation of a unique constraint?
I want to apologize for my bad english first. I am trying to implement DDD in my project, but I have some problems I will try to describe. I am developing a chat application. Front-end is quite simple
I would like to use EFf 4 as my ORM in my DDD project. I am going to generate 开发者_如何学Cmy model based on my classes.Should I create classes that are basically dto objects for my business objects
We have a complex aggregate (sensitive names obfuscated for confidentiality reasons). The root, R, is composed of collections of Ms, As, Cs, Ss. Ms have collections of other low-level details. etc et
My team is in the process of developing a system where we\'re using Unity as our IoC container; and to provide NHibernate ISessions (Units of work) over each HTTP Request, we\'re using Unity\'s ChildC
This question is a continuation of my previous question here zend models architecture (big thanks to Bill Karwin).
Most common ORMs implement persistence by reachability, either as the default object 开发者_StackOverflow社区graph change tracking mechanism or an optional.
i\'m not sure how to model this relationship... A cl开发者_如何学编程assroom contains many seats, every student studies in a classroom and have a favorite seat within it.
I am planning t开发者_如何转开发he implementation of an Inheritance Mapper pattern for an application component
I\'ve studied some CQRS sample implementations (Java / .Net) which use event sourcing as the event store and a simple (No)SQL stores as the \'report store\'.