#24727
Mentioned in 2 episodes
Domain-Driven Design
Tackling Complexity in the Heart of Software
Book • 2003
Domain-Driven Design (DDD) is a software design approach introduced by Eric Evans in 2003.
The book emphasizes the importance of understanding the business domain and creating software models that closely reflect this domain.
Key concepts include the use of a Ubiquitous Language, Domain Modeling, Entities, Value Objects, Services, Aggregates, and Repositories.
The book also discusses Bounded Contexts, which help in managing complex domains by decomposing them into smaller, more manageable parts.
Evans stresses the iterative process of refining the model through continuous collaboration between developers and domain experts, ensuring that the software design is driven by the domain rather than by technology or frameworks.
The book emphasizes the importance of understanding the business domain and creating software models that closely reflect this domain.
Key concepts include the use of a Ubiquitous Language, Domain Modeling, Entities, Value Objects, Services, Aggregates, and Repositories.
The book also discusses Bounded Contexts, which help in managing complex domains by decomposing them into smaller, more manageable parts.
Evans stresses the iterative process of refining the model through continuous collaboration between developers and domain experts, ensuring that the software design is driven by the domain rather than by technology or frameworks.
Mentioned by
Mentioned in 2 episodes
Mentioned by Austin Chadwick as a book he has read, relating to his experience of having a domain expert in the mob.
The DDD Dream? A Domain Expert Full-Time in a Mob 🚀
Mentioned as the creator of domain-driven design, a software design approach.
How does executable specifications compare with other modeling paradigms?
