|
- 一文读懂：领域驱动设计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)
- 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
- 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
- DDD and MVC: Difference between Model and Entity
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) The Entity has a life-cycle -- it's values can change throughout the course of the action -- and then it's saved or discarded
- Where to put business logic in DDD - Stack Overflow
If you put all your business logic in an (implicitly stateless) service layer you're writing procedural code By decoupling behavior from data, you're giving up on writing object-oriented code That's not always bad: it's simple, and if you have simple business logic there's no reason to invest in a full-fledged object-oriented domain model The more complex the business logic (and the larger
- DAO, Repositories and Services in DDD - Stack Overflow
After reading several articles, I am starting to understand the difference between DAO and Repositories, but I find myself in trouble trying to understand the difference between Repositories and Se
|
|
|