Domain-Driven Design: Tackling Complexity in the Heart of Software 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
There is a newer edition of this item:
Frequently bought together
From the Publisher
From the Back Cover
“Eric Evans has written a fantastic book on how you can make the design of your software match your mental model of the problem domain you are addressing.
“His book is very compatible with XP. It is not about drawing pictures of a domain; it is about how you think of it, the language you use to talk about it, and how you organize your software to reflect your improving understanding of it. Eric thinks that learning about your problem domain is as likely to happen at the end of your project as at the beginning, and so refactoring is a big part of his technique.
“The book is a fun read. Eric has lots of interesting stories, and he has a way with words. I see this book as essential reading for software developers―it is a future classic.”― Ralph Johnson, author of Design Patterns
“If you don’t think you are getting value from your investment in object-oriented programming, this book will tell you what you’ve forgotten to do.
“Eric Evans convincingly argues for the importance of domain modeling as the central focus of development and provides a solid framework and set of techniques for accomplishing it. This is timeless wisdom, and will hold up long after the methodologies du jour have gone out of fashion.”― Dave Collins, author of Designing Object-Oriented User Interfaces
“Eric weaves real-world experience modeling―and building―business applications into a practical, useful book. Written from the perspective of a trusted practitioner, Eric’s descriptions of ubiquitous language, the benefits of sharing models with users, object life-cycle management, logical and physical application structuring, and the process and results of deep refactoring are major contributions to our field.”― Luke Hohmann, author of Beyond Software Architecture
"This book belongs on the shelf of every thoughtful software developer."
"What Eric has managed to capture is a part of the design process that experienced object designers have always used, but that we have been singularly unsuccessful as a group in conveying to the rest of the industry. We've given away bits and pieces of this knowledge...but we've never organized and systematized the principles of building domain logic. This book is important."
--Kyle Brown, author of Enterprise Java™ Programming with IBM® WebSphere®
The software development community widely acknowledges that domain modeling is central to software design. Through domain models, software developers are able to express rich functionality and translate it into a software implementation that truly serves the needs of its users. But despite its obvious importance, there are few practical resources that explain how to incorporate effective domain modeling into the software development process.
Domain-Driven Design fills that need. This is not a book about specific technologies. It offers readers a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software development.
Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis--refactoring not just the code but the model underlying the code--in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. Domain-Driven Design then builds on this foundation, and addresses modeling and design for complex systems and larger organizations.Specific topics covered include:
- Getting all team members to speak the same language
- Connecting model and implementation more deeply
- Sharpening key distinctions in a model
- Managing the lifecycle of a domain object
- Writing domain code that is safe to combine in elaborate ways
- Making complex code obvious and predictable
- Formulating a domain vision statement
- Distilling the core of a complex domain
- Digging out implicit concepts needed in the model
- Applying analysis patterns
- Relating design patterns to the model
- Maintaining model integrity in a large system
- Dealing with coexisting models on the same project
- Organizing systems with large-scale structures
- Recognizing and responding to modeling breakthroughs
With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations.
About the Author
Eric Evans is the founder of Domain Language, a consulting group dedicated to helping companies build evolving software deeply connected to their businesses. Since the 1980s, Eric has worked as a designer and programmer on large object-oriented systems in several complex business and technical domains. He has also trained and coached development teams in Extreme Programming.
- Publisher : Addison-Wesley Professional; 1st edition (August 20, 2003)
- Language : English
- Hardcover : 560 pages
- ISBN-10 : 0321125215
- ISBN-13 : 978-0321125217
- Item Weight : 2.43 pounds
- Dimensions : 7.2 x 1.5 x 9.4 inches
- Best Sellers Rank: #29,053 in Books (See Top 100 in Books)
- Customer Reviews:
About the author
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Its strength is in delineating how the programmer is to relate to the domain experts who teach the programmer about the application area. He defines the term “ubiquitous language” to describe the language and concepts the two must share. I like this concept, but I think that the chosen wording should be “common language” instead of referring to the concept of ubiquity (whose meaning is closer to everywhere than shared or common).
This book had its time and place. However, for the $50+ price current on the market, I suggest that its time and place has passed. It has contributed to history, and one should appreciate those effects. Nonetheless, contemporary design concepts – like Agile development or the DevOps movement – certainly deserve more attention from the reader.
With fast pace of modern software development, it’s easy to forget that the main part of software value is in its “brains”. You can change GUI technology or infrastructure layer. You even can totally rewrite your application but the application domain stays more or less the same and at the end of the day the model defines whether this software is useful or not.
I can say that this book is targeting architects, domain experts, business analysts (and I believe these professionals are the main audience) but this would be the usual fallacy of separating software developers into first and second class. So I say the opposite – if you want to transcend from craft of software development to its art you should read this book.
Not just about code. Lots of content on how to organize teams around business value, and how that is reflected in the design of your system.
The only thing keeping me from a 5th star is that it can be a very dry book in certain areas. There also could have been more code samples and less UML and walls of pure text.
Bounded contexts are the most important concept to take away from this book.
If you're on the fence, go and check out Eric Evans' talks on YouTube.
Great work nonetheless!
Top reviews from other countries
I’ve now read it once and know I will be reading it cover to cover again. For me it is the right place to start learning about DDD but as Evans admits himself it perhaps lacks some practical guidance on how to go about actually doing DDD for real, in respect to the implementation of software that is as this book is about a philosophy, not technical details. My advice is to try and read it as fluently as it is written, and it is very fluently written, and don’t worry too much that all of its detail is not going in. As I said, this is a difficult subject. Once you’ve read it, read one of the books that takes the material and treats it in a less formal way but a more practical hands on way, I’m doing that right now, then read the Evans again with the context that you’ll get from the less formal book will turbocharge your understanding, well that’s the basis I’m working on :)
Becoming proficient at DDD takes time and work but I suspect the rewards are, as I suggested, game changing.
Already I am looking at code and the way a business is structured to attempt to produce code with the blinkers off and a much clearer picture of the pros and cons of what I see.
For me there are but a few seminal books on writing software and having read this one I’m putting it right up there with the very, very best of them.
Absolutely loved every page.
This book deserves respect for the new paradigm being described and the clear and well structured way it has been described and explained.
Its very possible you may need to have a certain level of experience and knowledge to get the most out of this book, but I think anyone who carefully reads the book, and looks up the things they may not be familiar with, will gain a great understanding of the subject.
Do not expect to be an expert on the first few readings. First read it and understand the core concepts. After that using these ideas and approach on real projects, requires commitment and patience. The author says it's not easy to implement, but it is very effective and provides a solid long term approach.
DDD might not be for all projects, but all software developers, and project managers should be aware of this paradigm and recognise the importance which DDD has.
However, I find this book so hard to read at the same time. It's a great topic and all developers need to understand this modelling technique properly as this is the basis of the new age of software development. But it lacks analogies and a range of examples to better explain what he means, which means that he uses a very terse descriptive that is hard to process. I think several people should've written it and put in their experiences of the approaches they used and their experiences.
The first quarter of the book is particularly annoying as it talks about what you are about to learn all the time. I think he also means for it to be used as a reference, but it's far too verbose and waffly and not split up enough conceptually to be useful for that.
Great for developing systems in an agile way. DDD requires huge team work and cooperation, courage and tremendous amount of practice.
As with other outstanding books, within many decades it will still be up-to-date, relevant and ignored by many.