What is Domain Driven Design? - Stack Overflow DDD (domain driven design) is a useful concept for analyse of requirements of a project and handling the complexity of these requirements Before that people were analysing these requirements with considering the relationships between classes and tables and in fact their design were based on database tables relationships it is not old but it has
DDD: guidance on updating multiple properties of entities DDD is better suited for task-based UIs What you describe is very CRUD-oriented In your case, individual properties are treated as independent data fields where one or many of these can be updated by a single generic business operation (update) You will have to perform a deeper analysis of your domain than this if you want to be successfull with DDD Why would someone update all those
DDD: should entities contain or reference other entities? DDD is a design concept that states that you should create a single unit of code (called the domain) which contains all code related to modeling your business concepts, and business rules constraints associated to them
O que realmente é DDD e quando ele se aplica? O que é DDD? Domain-Driven Design (DDD) é uma abordagem de desenvolvimento de software em que o design é orientado pelo domínio, ou seja, pela área de conhecimento à qual o software se aplica Outra forma de dizer é: em DDD, o design da solução é orientado pelas regras de negócio Não significa que outros aspectos do software como persistência ou modelagem de dados sejam ignorados
DDD - Persistence Model and Domain Model - Stack Overflow In DDD, are persistence model and domain model different things? Yes, but that does not necessarily imply a different set of classes to explicitly represent the persistence model If using a relational database for persistence an ORM such as NHibernate can take care of representing the persistence model through mappings to domain classes