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. Before attempting ddd, you should be familiar with design patterns and enterprise design patterns Knowing these makes ddd a lot easier to grasp And, as mentioned above, there is a free introduction to ddd available from infoq (where you can also find talks about ddd). 领域驱动设计DDD越来越受到重视， 国内有很多团队在使用领域驱动设计DDD， 但是每一个团队对DDD的理解可能不一样。 如果领域的设计不能很好地指导开发工作， 那么DDD的威力就发挥不出来了。 我们接触到的“领域驱动”， 很有可能是假的“领域驱动”， 是别人理解消化后的领域驱动， 即使是. Asked 4 years, 7 months ago modified 1 year, 8 months ago viewed 11k times
In ddd, there is also the concept of a domain entity, which has a unique identity to it As i understand it, a user is a good example of an entity (unique userid, for instance) Api clients should be designed with domain in mind too Otherwise you lose most of benefits of ddd. The dto implementation seems part of the domain, but it means that when i create a collection of dtos in the service layer and pass it to a presentation layer, i have to reference domain layer in presentation layer, which seems wrong What is the correct way to implement dto using ddd principles?
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. Sure you can probably just add a repository interface to entity a for reading entities b But the risk is that you expose knowledge for how to persist b.
OPEN
