I think a lot of people suggest Patterns, Principles, and Practises of Domain Driven Design instead. The Evans book is sort of written backwards, in that it st

I think a lot of people suggest Patterns, Principles, and Practises of Domain Driven Design instead. The Evans book is sort of written backwards, in that it starts with a bunch of powerful tactical tools and people stop reading halfway through which means now all they have is a hammer. The PPPoDDD book instead starts out with reasoning about when DDD is appropriate and when it's not, to dive into the tactical patterns last, once the other options are eliminated. I think that approach makes much more sense. After all, most of the skill in a technique consists in knowing when to apply that technique, and, critically, when not to. The PPPoDDD book also places a heavy emphasis on having productive conversations with businesspeople as a design tool. I think Evans accidentally underemphasises that too.