Hide this

Results from Google Books

Click on a thumbnail to go to Google Books.

Domain-Driven Design: Tackling Complexity in…

Domain-Driven Design: Tackling Complexity in the Heart of Software (edition 2003)

by Eric Evans

MembersReviewsPopularityAverage ratingMentions
536518,778 (4.3)1
Title:Domain-Driven Design: Tackling Complexity in the Heart of Software
Authors:Eric Evans
Info:Addison-Wesley Professional (2003), Hardcover, 560 pages
Collections:Your library

Work details

Domain-Driven Design: Tackling Complexity in the Heart of Software by Eric Evans



Sign up for LibraryThing to find out whether you'll like this book.

No current Talk conversations about this book.

» See also 1 mention

Showing 5 of 5
  Ovi_Books | Jun 6, 2010 |
On a topic which most authors would probably tend to evangelize, Eric Evans is conversational. His viewpoint is straightforward: these are the principles he feels he's extracted from putting in many, many hours on many, many projects. But he sort of slip-slides around the principles, approaching them from the back with lots of digressions on things his teams have tried; sometimes they work and sometimes they don't work, and maybe this general principle is sort of, kind of, why the ones that worked, did. Which is a bit of a breather if you're used to the typical snake-oil agile style where JOE USED ALL THE AGILE PRINCIPLES AND BROUGHT IN HIS PROJECT 30% UNDER BUDGET!

But Domain-Driven Design is tricky, much more so than the simple agile recipes like test-driven development and pair programming. DDD is much more about finding common ground with the people who use your software, or at least the people who represent those people, and so it's almost more a book on communication than it is on coding. But it isn't. Evans sticks strictly to the coder side of it, and focuses on how one extracts business logic and rules from business people, even when those people aren't completely clear on the rules themselves, which is most of the time.

So if you're the type of developer who just wants a spec to work from, and to be able to tell the boss, "can't change that - it's just like the spec says", feel free to skip this book. If you think domain levels are a waste of time, and you're happy with a UI layer that talks directly to the database layer, go ahead and skip this book.

But if you think that communicating with the people that actually use your software is important, or if you see software as a way to model business functionality, it's a must read. Because without some inkling of these principles, no piece of complicated, useful software could ever come into being. ( )
2 vote benfulton | Feb 20, 2009 |
Following on from the original Design Patterns book by the Gang of Four this is a must read for anyone serious about taking the development to the next level. ( )
  naeemis | Oct 19, 2008 |
Clever and clear, even if somewhat slow-moving. Eric Evans knows where to lead the reader, and the book is full with plenty of useful insights. ( )
  ziobrando | Mar 11, 2007 |
Showing 5 of 5
no reviews | add a review
You must log in to edit Common Knowledge data.
For more help see the Common Knowledge help page.
Series (with order)
Canonical title
Original title
Alternative titles
Original publication date
Important places
Important events
Related movies
Awards and honors
First words
Last words
Disambiguation notice
Publisher's editors
Publisher series
Original language

References to this work on external resources.

Wikipedia in English (3)

Book description
Haiku summary

No descriptions found.

No library descriptions found.

Quick Links

Swap Ebooks Audio
42 wanted

Popular covers


Average: (4.3)
1 1
2 1
2.5 1
3 9
3.5 2
4 32
4.5 6
5 41

Is this you?

Become a LibraryThing Author.


You are using the new servers! | About | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 115,146,154 books! | Top bar: Always visible