|
- 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 - 知乎
领域驱动设计（DDD）前些年很火，因为近两年2B和SAAS越来越受关注。但不少人读过Eric Evans的《领域驱动设计》和Vaughn Vernon的《实现领域驱动设计》后，都表示很懵，太抽象了。
- 能否用一个简单的实际业务场景通俗易懂的解释DDD（领域驱动设计）该如何正确的使用？ - 知乎
由于业务场景或者技术条件的限制，有的可能用 NET，有的则是 Java，有的甚至大数据架构。 对于这些存在技术异构的功能，可以考虑按照技术边界进行拆分。 5、其他 效率问题 虽然DDD有这么多明显的优势，但也不是所有的系统都适合采用DDD领域驱动设计。
- Can you suggest DDD best practices - Stack Overflow
The first best practice I can suggest is to read the Evans' book Twice Too many "DDD projects" fail because developers pretend that DDD is simply OOP done right Then, you should really understand that DDD is for applications that have to handle very complex business rules correctly In a nutshell: if you don't need to pay a domain expert to understand the business, you don't need DDD The
- 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
- Differences between DDD MDD - Stack Overflow
Domain Driven Design (DDD) Model Driven Design (MDD) I always find these two terms in many articles and public literature, but no one highlights the differences
- DDD - which layer DTO should be implemented - Stack Overflow
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?
|
|
|