- Hardcover: 560 pages
- Publisher: Addison Wesley; 1 edition (20 Aug. 2003)
- Language: English
- ISBN-10: 0321125215
- ISBN-13: 978-0321125217
- Product Dimensions: 18.5 x 3.6 x 23.6 cm
- Average Customer Review: 4.2 out of 5 stars See all reviews (26 customer reviews)
- Amazon Bestsellers Rank: 82,044 in Books (See Top 100 in Books)
- See Complete Table of Contents
Domain-driven Design: Tackling Complexity in the Heart of Software Hardcover – 20 Aug 2003
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Frequently Bought Together
Customers Who Bought This Item Also Bought
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 e-mail address or mobile phone number.
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.
Inside This Book(Learn More)
What Other Items Do Customers Buy After Viewing This Item?
Top Customer Reviews
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.
The book is written superbly. Eric breaks down various parts of the domain into categories and describes what they are, their benefits and relation to the whole picture in a way that just makes sense. I have used the techniques and they simplify the design and make it possible to go straight to a domain expert and take software instead of having to talk 2 seperate languages.
I dont find the book hard to read at all, and im not overly educated. If you want an example of hard to read, GangOfFour; a fantastic book but not easy reading. This book is written well, full of experience and well worth a read.
Buy this book..it's worth it. If your worried about it being a length read, you can go to the domain driven design site and they have a concise version of the patterns to read. But I highly recommend that you get the book and read it from cover to cover.
* I wish more companies adopted this philosophy, instead of the "if it ain't broke don't fix it approach". I thoroughly agree with the refactoring approach as it leads to other breakthroughs and the simplification pays of dividends in the end in the maintenance cycle of a project.
* This book is complemented well by Martin Fowler Refactoring and Analysis Patterns books.
* If your are into Agile, Test Driven Development or Extreme Programming you will find this book gives you more "bang for your buck".
* There is a good blend of architectural concepts. I particularly found his discussion on the aggregate and specification patterns most enlightening and will be able to use them in future projects.
* I'd love to work with Eric on a project some day. This would be my idea of Nirvana! :)
The writing style is excellent, the ideas are interesting, the persentation is superb and (most importantly) good examples are provided along the way.
Most Recent Customer Reviews
I have read many technical books, but I've never read anything as badly written as this. The book is full off uncertainties, sentences that can be taken out completely as they add... Read morePublished 12 months ago by vikpea
As I read this book my heart sang. The writing is clear, subtle ideas are articulated well, and the entire book is packed with gems of outstanding quality and brilliance. Read morePublished 20 months ago by Alastair
A must read book for those with some experience in software development. You can find valuable explanation of real life issues you face every day when designing or developing... Read morePublished on 17 July 2013 by JS
Some software books teach you have to program in language A, some teach you the pitfalls of language B, some are more general and cover a paradigm. Read morePublished on 25 April 2013 by TruffleMuffin
Product arrived quickly and as described. Only minimal usage and thankfully no notes on any of the content pages, I do however agree with your thoughts on the Foreword!Published on 10 Jan. 2013 by Mark Walsh
As you are reading it, it seems to take an age to get to 'the good stuff', and I agree that the chapters concerning bounded contexts etc could do with being nearer the front.Published on 7 Dec. 2012 by Toby