|
- 一文读懂：领域驱动设计DDD - 知乎
领域驱动设计（DDD）前些年很火，因为近两年2B和SAAS越来越受关注。但不少人读过Eric Evans的《领域驱动设计》和Vaughn Vernon的《实现领域驱动设计》后，都很懵，太抽象。 本文在介绍领域驱动设计的基本概念的同时，用一个虚拟的公司和一个虚拟的项目，介绍领域驱动设计的落地实践，帮助大家了解
- 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
- What is Domain Driven Design (DDD)? - Stack Overflow
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 Hexagon - Should the Domain Layer ever talk to the Infrastructure . . .
DDD Hexagon - Should the Domain Layer ever talk to the Infrastructure (DAL) Layer in any situation? Asked 4 years, 8 months ago Modified 1 year, 9 months ago Viewed 11k times
- domain driven design - Rest API and DDD - Stack Overflow
Domain-driven design is about domain API clients should be designed with domain in mind too Otherwise you lose most of benefits of DDD
- python - Django and domain driven design - Stack Overflow
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
- DDD - the rule that Entities cant access Repositories directly
Important with DDD is that each entity has a responsibility to manage its own "knowledge-sphere" and shouldn't know anything about how to read or write other entities 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
- DDD - Dependencies between domain model, services and repositories
To your last point, services in DDD are a place to put what I describe as "awkward" logic If you have some type of logic or work flow that has dependencies on other entities this is the type of logic that usually doesn't "fit" inside a domain object itself Example: If I have a method on my business object to perform some type of validation, the service class might execute this method (still
|
|
|