Domain Driven Design Vs Clean Architecture
Software should be like waffles not.
Domain driven design vs clean architecture. In this respect my architecture is more conservative than other clean ddd solutions the domain layer should only be concerned with business logic and interaction among domain entities. Domain driven design is hard to differentiate from clean architecture. Let s see how 2 fabulous architectures approach this problem.
So eric evans makes a clear declaration on the matter. By context we mean sub domain department. One of the first architects who defined domain driven design principles was eric evans.
Clean architecture domain driven design. The reason is that the most of business logic is included in aggregates entities and value objects. Eventually i ended up reading clean architecture by uncle bob and then domain driven design by eric evans.
I spent a lot of time doing rework writing untestable code trying to invent my own bad abstractions and putting all my business logic into anemic services. Common architecture with domain driven design model is presented on the right side of the picture. Ddd focus is to understand what the application should do and translate that to code providing a lot of insights on how you should organize the business rules and data models.
Objects are context bound. Before i got into software design and architecture my code was hurting. Domain driven design by eric evans and clear architecture by robert c.
Domain driven design initially written in 2003. As i already stated clean architecture was the main reason i started this journey. The book features several parts.