Home > Book, DDD, Review > Book Reviewed: Domain-Driven Design: Tackling Complexity in the Heart of Software by Eric Evans

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

June 15th, 2009

Eric Evans Domain Driven DesignIn Domain-Driven Design: Tackling Complexity in the Heart of Software Eric Evans shares his extensive development and consulting experience as he outlines his approach to software development and design using Domain Driven Design (DDD). Evans’ writing style is easy to read as he maintains a comfortable conversational tone while pragmatically guiding us through the many patterns and concepts that encompass DDD. However; be-warned the concepts that lie within are occasionally dense, abstract, but ultimately enlightening as Evans’ forces us to look at development from a new perspective.

It’s also fair to mention that this book has been charged as being just another patterns book, and while I can see this perspective, some of the concepts do come across as being overly abstract without clear implementations (code) to reference, but this books is much more than another patterns book. As a developer you don’t want to overlook this book, it’s an insightful snapshot into the mind of an experienced developer. From my experience the concepts and patterns surrounding Domain Driven Design frequently crop up in Service Orientation, MVC/MVP structured Web Applications, Object Orientation, Test Driven Development, Model Driven Development, and other modern staticly typed best practices. If you do find yourself grasping for more concrete implementations then you’ll want to read Jimmy Nilsson’s Applying Domain-Driven Design and Patterns: With Examples in C# and .NET book too – Nilsson’s book provides many code examples while directly referencing Evan’s text.

I highly recommend this book, it’s a great reference to have alongside Steve McConnell’s Code Complete, Facts and Fallacies of Software Engineering by Robert Glass, and the Martin Fowler blessed books too.

A group of us reread this book as part of The Calgary Book Club. View my review on Amazon.

Author: Adam Kahtava Categories: Book, DDD, Review Tags:
  1. Ruz Safai
    June 15th, 2009 at 17:17 | #1

    I haven’t read Evan’s Domain Driven Design yet, but I’ve read the condensed version Domain Driven Design Quickly and it really made me appreciate the old days where I used to be both a developer and Business Analyst, since the code reflected the domain much more closely.
    I wrote an Access database about 8 years ago that’s still used today as a client’s primary application (never had a need to convert it to .net or anything), and it wouldn’t have lasted a fraction of the time had I not understood the domain before hand. A blog I saw yesterday mentioned that a developer is only coding about 25% of the time at most (the rest is discussions, reviews, meetings, etc.), so with the other time spending communicating they might as well be BA’s. The book is great if only for the fact that it makes developers really understand what they’re coding.

  2. Adam Kahtava
    June 16th, 2009 at 06:05 | #2

    Wow, that’s a great link. It’s the Coles notes / crib notes of Domain Driven Design. I wish I knew about it earlier.

    Being a developer is certainly not all about coding, it’s funny how we get caught up in micro efficiencies like refactoring tools, text editors, and keyboard commands.

    Thanks Ruz.

  1. No trackbacks yet.