- Hardcover: 560 pages
- Publisher: Addison-Wesley Professional; 1 edition (August 30, 2003)
- Language: English
- ISBN-10: 0321125215
- ISBN-13: 978-0321125217
- Product Dimensions: 7.2 x 1.4 x 9.4 inches
- Shipping Weight: 2.8 pounds (View shipping rates and policies)
- Average Customer Review: 105 customer reviews
- Amazon Best Sellers Rank: #27,247 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Domain-Driven Design: Tackling Complexity in the Heart of Software 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
"Neverworld Wake" by Marisha Pessl
Read the absorbing new psychological suspense thriller from acclaimed New York Times bestselling author Marisha Pessl. Learn more
Frequently bought together
Customers who bought this item also bought
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.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
I suppose what blew me away was that Evans crystallized and laid out quite clearly about a dozen ideas which were existing at the edge of my consciousness, but which I could not clearly verbalize.
It fits quite nicely between the patterns books and the process books, but it's not a cookbook and it's not strictly a method. It's a must read for the multitude of Java/C#/C++ developers who continue to write procedural code while claiming they're OO developers because they're using an OO language and they've read Design Patterns.
There is nothing new in this book -- but you really should read it.
This book details the way many architects and analysts have been creating their applications for years, and for good reason. They start by creating domain classes that help represent data in a way that is understandable to both developer and customer. Then building out the application from there.
Read this book.
In particular, the Repository and Aggregate patterns interests me, but there are many problems that arise when trying to implement a Repository that can handle saving and updating entire Aggregates while keeping the Entities isolated from the persistence mechanism. This is a topic for a tech blog, and in searching the 'net, plenty of them are discussing it. No one seems to have answered the implementation question, though.
The book is also a bit repetitive and verbose. I didn't find the sections on ubiquitous language very helpful. Engineers and non-engineers don't approach problems the same way, common language or not. I didn't feel that added much to the technical design discussions that followed.
If I ever figure out a practical implementation of the ideas, I may come back and give the book another star.