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. Can someone explain the difference between domain and application services by providing some examples Before attempting ddd, you should be familiar with design patterns and enterprise design patterns
Thedandangler aka https: Nude Leaks OnlyFans/Patreon Photo #627 - Faponic
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).
Asked 4 years, 5 months ago modified 1 year, 6 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) Please note 'model' in ddd is 'domain model' which consists of entities, value objects, services, repositories, aggregates, aggregate roots and whatever else is needed to represent the domain in question
Model in django models, are entities In other words, in ddd, model is a model of the domain. 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? 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.
