Members with This Book
Most Helpful Reviews
see all reviews
Liked It “I am re-reading the book. I am emphasizing the part IV (almost 1/3 of the book) called 'Strategic Design'. All I can say is, this book is gold. Although, Mr. Evans's writing style is not very easy for people like me whose first language is not English. Anyway, reading this book slowly is another...” see full review » see other reviews » |
Newest Reviews
see all reviews-
“I am re-reading the book. I am emphasizing the part IV (almost 1/3 of the book) called 'Strategic Design'. All I can say is, this book is gold. Although, Mr. Evans's writing style is not very easy for people like me whose first language is not English. Anyway, reading this book slowly is another kind of way to really get the handle of it.”
Harry C wrote this review Wednesday, April 29 2009. ( reply | permalink ) Was this review helpful? Yes | No
“A must-read for every software developer. Eric introduces building blocks of software design on a less technical level that the GOF does for example, thus trying to tackle complexity by finding more domainic terms, more domainic models.
Oliver Gierke wrote this review Sunday, January 4 2009. ( reply | permalink ) Was this review helpful? Yes | No
A shorter version of the book can be found at http://www.infoq.com/minibooks/domain-driven-design-quickly. So i suggest to read the intro first and then take a deep dive into the book itself as it is very detailed.”
“First, this is a good book. I'm new to the domain-driven space and formal OO design so this way a big bite for me. But I know this is a seminal text so I decided to give it a try.
Andy Merrick wrote this review Tuesday, December 23 2008. ( reply | permalink ) Was this review helpful? Yes | No
If you're also new to DDD, you WILL learn from this book, but you will NOT be an expert at the end. In fact, the concepts presented in this book have confused me even more. This is not a knock on Evans, but a commentary on how unfamiliar some of these ideas are to me.
With that said, Evans has given me a whole new set of categories and vocabulary into which I can begin to fill in the missing pieces. This is the process of learning!
His examples in the book are from real life but the domain knowledge (e.g. shipping industry, circuit board printing, etc) necessary to understand them is sometimes substantial. This makes understanding his main point tough because you can't see how it actually works out in real life (since you can't understand the example), so his point remains an abstraction you also can't understand. But I don't blame him for this. We developers will either complain that an example is too arbitrary (animals/cats/dogs when discussing polymorphism) or too specific (as is the case in many of his examples). Only ~30% of his examples fall into this category.
One thing I would strongly recommend before reading this book is to have read a book on patterns and understand what they are, why they're used, and even some specific examples of patterns, namely, the repository, strategy/policy, and specification patterns. It will help you to understand extended sections of the book with more clarity.
In all, I think this is a good book. Knowing what I know now, I would definitely read it again. When I gain more insights into DDD, I may come back and read it again.”“A bit long, although extensive, needs to be more consice, with less words to emphasize the point; also better diagrams + code would be helpful.”
cDima wrote this review Monday, May 19 2008. ( reply | permalink ) Was this review helpful? Yes | No“This book is not really 'an easy read'. It is definitely not a book that you should read just before going to sleep.
Frederik wrote this review Saturday, December 30 2006. ( reply | permalink ) Was this review helpful? Yes | No
I'm not saying that this book is not well written; it's rather the content of the book that's quite heavy (which does not mean that it is not interesting offcourse).
This book contains some very valuable information, and I consider this book as one of my 3 bibles. (The other 2 are the GoF design patterns book, and Martin Fowler's Patterns of Enterprise Architecture).
If you're interested in Domain Driven Design or want to develop enterprise applications in an OO fashion with a rich domain model, then this book is definitely a *must have*.
But, because of the though material, I would also recommend Jimmy Nillson's 'Applying Domain Driven Design' book, to have it next to Domain Driven Design. I find this book (Domain Driven Design) sometimes a bit to abstract, and then it is helpfull to have Jimmy Nillson's book alongside.”
Displaying 1-5 of 5
