If your process for writing an application is to start with the database, or to start designing UI, you should read this book.

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.

This book is just amazing. In this design world, there is so much to look for, and this guy just brings it all into one book. He answers the questions you have been asking. He compiled a lot of knowledge people already had into a wonderful set of ideas. Get it.

In my idea, it represents "The book" that each developer who wants approach Domain Driven Design methodology must have in his own books collection.

This book is one the few I have been reading and re-reading since it was published back in 2004. Unlike XP and Agile titles which describe the Bleeding Obvious in numerous tomes, Domain-driven design takes a deep dive into stuff that makes designing and writing software a rewarding experience: understanding the technical problem at hand and then finding an optimal solution.

Too many technical books are written for people who should not be writing software in the first place. This one was written for enthusiasts and professionals alike.

Note to publisher: an electronic version would be nice-to-have.

Domain Modeling is the backbone for any non trivial application. Most pattern books concentrate more on behavioral aspects of the application rather than talk about the design of the core domain model. This book fills this need and does it in a very commendable way.

That Eric Evans is an agile practitioner and a great crafter of domain models, becomes evident in this book. He transforms the art of designing a domain model into more like a science. He illustrates his points with numerous practical examples.

I use some sample "requirements capturing conversations" that Eric talks about in this book as excellent examples to illustrate the need for a domain model.

This book is a must have in every architect's book shelf.

Update:
I find it very hard to read this book from cover to cover tho. Since this book is about sound design principles,it has to be much more interesting than what it turns out to be! But still there is tons of information. Hard to get that kind of information from anywhere else.