@kenny_baas
@
[email protected]
Domain-
Driven Design presents an all-
encompassing view on software design. It considers
design from the micro-
level of code and design patterns, to models and their language, to
communication and relationships between models, to the large scale reasoning about
systems of systems. On top of that, it aims to be pragmatic. You don’t apply DDD
everywhere, you do it where it will have the most impact.
DDD is not prescriptive. It doesn’t have rules of how to do it, and is open to new
interpretation. It doesn’t prescribe methods, or practices, and even the patterns in the
book1 are meant to be illustrative rather than a final set. Many methods that people now
consider core to DDD, such as EventStorming, didn’t exist when the book was written.
Important Notes
verraes.net
What is Domain-Driven
Design (DDD)
Domain-Driven Design is a software
design discipline centred on the
principles that: Software for a complex
domain requires all designers
(engineers, testers, analysts, ...)