Domain-Driven Design Review
Join the DZone community and get the full member experience.Join For Free
a brief summary
ddd is a very dense book, and it is logically divided in four parts:
- putting the domain model to work , which covers the importance of the ubiquitous language and the centrality of the model of the application domain.
- the building blocks describes the patterns used at the finer level, such as entity, value object, aggregate, service, factory and repository.
- refactoring towards deeper insight covers the continuos process of adapting the domain model to new insights and crunched knowledge, believing firmly that an hidden model exists and will be reached with a supple design. modelling as described here is like applying an unification theory to software.
- strategic design introduces the techniques for large scale structure and separation of contexts, such as the famous anticorruption layer (although it is not the only communication medium between different domain models.)
in my opinion the third and fourth parts are the most difficult to
digest, due to their abstractness (not everyone of us has worked at that
scaling level) and the perceived distance from working code. in fact,
the first two parts are rich in code samples, which gradually vanishes
towards the end of the book while the view on object-oriented
applications is taken to an higher level. diagrams, both based on uml
and not, are preferred throughout the last chapters.
how to read it
many people start reading ddd full of confidence, scheduling five chapters a day, only to struggle very quickly, usually in the second part, and abandone it. even in my recently completed reading from cover to cover, i waited some time before starting the third part.
this book is intended as a series of patterns - notice the capital letters used for most of the names - those names are specific terms with a precise meaning. in the case of the gang of four book on design patterns, this made it hard to read cover to cover because of the lack of a common thread between the chapters.
but in this book's case, the main theme is the model-driven design practice that evolves from the finest level - the class and its methods - to boundedcontexts and responsibility layers. that said, the information contained is very dense and i have never read more than 15-20 pages on a given day. i suggest you do to the same or you risk burning out before reaching half of the book. also taking notes is a mean that forces high focus of the content and may help.
there is a lighter book freely available - domain-driven design quickly - which promises to explain you ddd in 100 pages. don't read it: when i tried, i understood a concept only as long as i have already read it on the original ddd book, and never learn anything on the new material. the original is 400-page long, but it is already condensed as much as possible.
a book that expands on the code samples and the design process is applying domain-driven design and patterns , which is a good read to combine with ddd (in fact, it is 600-page long.) you may refer to it when you want more practical examples of a pattern treated in the original book.
in sum, this book is often cited as the ddd book, and in the future it may be considered the bible of real object-oriented development. if you have it on your shelf, i suggest you to read as much as you can beginning from the start, skipping only the fourth part if you do not ordinarily deal with large-scale applications.
Published at DZone with permission of Giorgio Sironi, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.