
Enjoy fast, free delivery, exclusive deals, and award-winning movies & TV shows with Prime
Try Prime
and start saving today with fast, free delivery
Amazon Prime includes:
Fast, FREE Delivery is available to Prime members. To join, select "Try Amazon Prime and start saving today with Fast, FREE Delivery" below the Add to Cart button.
Amazon Prime members enjoy:- Cardmembers earn 5% Back at Amazon.com with a Prime Credit Card.
- Unlimited Free Two-Day Delivery
- Streaming of thousands of movies and TV shows with limited ads on Prime Video.
- A Kindle book to borrow for free each month - with no due dates
- Listen to over 2 million songs and hundreds of playlists
- Unlimited photo storage with anywhere access
Important: Your credit card will NOT be charged when you start your free trial or if you cancel during the trial period. If you're happy with Amazon Prime, do nothing. At the end of the free trial, your membership will automatically upgrade to a monthly membership.
Buy new:
$59.99$59.99
FREE delivery:
Saturday, March 23
Ships from: Amazon.com Sold by: Amazon.com
Buy used: $54.92
Other Sellers on Amazon
& FREE Shipping
79% positive over last 12 months
+ $3.99 shipping
95% positive over last 12 months

Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Domain-Driven Design: Tackling Complexity in the Heart of Software 1st Edition
Purchase options and add-ons
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.
- ISBN-100321125215
- ISBN-13978-0321125217
- Edition1st
- PublisherAddison-Wesley Professional
- Publication dateAugust 20, 2003
- LanguageEnglish
- Dimensions7.4 x 1.4 x 9.55 inches
- Print length560 pages
Frequently bought together

More items to explore
- A model is a selectively simplified and consciously structured form of knowledge.Highlighted by 1,618 Kindle readers
- The heart of software is its ability to solve domain-related problems for its user.Highlighted by 1,488 Kindle readers
- If sophisticated domain experts don’t understand the model, there is something wrong with the model.Highlighted by 1,396 Kindle readers
From the Publisher

From the Foreword by Martin Fowler
"The key to controlling complexity is a good domain model, a model that goes beyond a surface vision of a domain by introducing an underlying structure, which gives the software developers the leverage they need. A good domain model can be incredibly valuable, but it’s not something that’s easy to make. Few people can do it well, and it’s very hard to teach.
Eric Evans is one of those few who can create domain models well. I discovered this by working with him—one of those wonderful times when you find a client who’s more skilled than you are. Our collaboration was short but enormous fun. Since then we’ve stayed in touch, and I’ve watched this book gestate slowly.
It’s been well worth the wait."
![]() |
![]() |
![]() |
|
---|---|---|---|
Domain-Driven Design Distilled | Domain-Driven Design | Implementing Domain-Driven Design | |
Customer Reviews |
4.4 out of 5 stars
567
|
4.6 out of 5 stars
1,333
|
4.5 out of 5 stars
596
|
Price | $36.63$36.63 | $59.99$59.99 | $58.06$58.06 |
Core DDD techniques for building better software | A systematic approach to DDDs for building better software | A top-down approach to understanding DDD | |
Overview | Concise, readable, and actionable guide to the basics of DDD: What it is, what problems it solves, how it works, and how to quickly gain value from it. | 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. | Building on Eric Evans’ seminal book, Vaughn Vernon couples guided approaches to implementation with modern architectures, highlighting the importance and value of focusing on the business domain while balancing technical considerations. |
What Will You Learn | Each core DDD technique for building better software. Never buries you in detail–it focuses on what you need to know to get results. | Design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. | Practical DDD techniques through examples from familiar domains and how to use DDD within diverse architectures, including Hexagonal, SOA, Rest, CQRS, Event-Driven, and Fabric/Grid-Based. |
Editorial Reviews
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."
--Kent Beck
"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.
Product details
- Publisher : Addison-Wesley Professional; 1st edition (August 20, 2003)
- Language : English
- Hardcover : 560 pages
- ISBN-10 : 0321125215
- ISBN-13 : 978-0321125217
- Item Weight : 2.73 pounds
- Dimensions : 7.4 x 1.4 x 9.55 inches
- Best Sellers Rank: #39,047 in Books (See Top 100 in Books)
- #10 in Computer Systems Analysis & Design (Books)
- #13 in Object-Oriented Design
- #39 in Software Development (Books)
- Customer Reviews:
Important information
To report an issue with this product or seller, click here.
About the author

Eric Evans is a thought leader in software design and domain modeling. The founder of Domain Language and author of Domain-Driven Design, he recently founded a modeling community where those interested in domain modeling can come together to learn and discuss effective practices. He’s worked on successful Java and Smalltalk projects in fields including finance, shipping, insurance, and manufacturing automation.
Eric looks for opportunities to help organizations to get more value from their software development efforts by connecting technical thinking with business thinking—and developing supple domain models that form the heart of software applications. He conducts workshops and coaches teams on strategic design and domain modeling. He aslo, mentors teams to smoothly mesh design and process best practices and bring those techniques to bear on effectively delivering core value.
For information on the trainings Eric and his staff provide, visit his website at www.domainlanguage.com.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Principles that must be present in a software project are highlighted (such as communication through a language used by all team members, a language that is built from discussions with domain experts). Importance of software design and how it favors problem solving and clear communication between team members and teams.
For a while I was looking at refactoring as a "thing to do when the software is done if time allows it", Eric Evans highlights refactoring as a necessity and must not be neglected because continuous refactoring leads to deeper knowledge and understanding of what the Software needs to do and how it actually does it.
Practical problems such as the possibility of multiple models to exist within the same system have been addressed and given solutions from using one common (unified) model in the whole system (also the costs of such a choice are presented) to totally independent models. An algorithm described in steps is presented for getting two totally independent models to be completely unified allows designers and developers to combine any part of their software towards new features required by the business.
Also a common problem at this time is integration with legacy systems (there are lots of systems that were written using old, now unreliable, components that need migration towards newer, safer, faster components), this problem is approached and it's solution is detailed from beginning to end where the system is completely migrated.
Last but not least, a small oriented graph is given to visualize how concepts in the book are connected and how all pieces fall into the puzzle. Any software developer should read this book at least one time.
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.
Every mid- to senior-level developer who is serious about their craft must read this book. I am confident that well written (i.e. SOLID), maintainable software is impossible to achieve without a model-driven design perspective. Simply using "design patterns" is not enough. This book gives you the knowledge behind model-driven design (or Domain-Driven design) and how to apply it (albeit in abstract ways--as every software project and its requirements are different--better stated, you just need to practice the concepts within and gain experience with them in order to more effectively use them over time).
I read a copy of this years ago, but at my level of software development maturity, I was not ready for the concepts presented and found it difficult to read. Having a few more years under my belt, I decided to purchase my own copy (Hardback, no less!!) and immediately began to read it again. I am truly excited about what I'm (re)learning in this book and can't wait to begin trying to view software systems and business requirements through the lens of model-driven design.
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.
Top reviews from other countries





De principio a fin conecta todos los apartados y elementos que el autor quiere discutir sobre el diseño de productos/programas basados en el dominio, como afrontar cambios en las implementaciones y como analizar debidamente los diferentes problemas que pueden salir de los desarrollos.
Eso si, el lenguaje no es bàsico y se necesita un buen nivel de inglés para un buen entendimiento.
(Juraria que existen ediciones en castellano/catalan, pero no sé que editoriales las han hecho)