>I'd say part of the problem is that DDD critics conflate DDD with overly complex, enterprisey models
Every text I've ever written on DDD has made it pretty clear that these patterns are at the very heart of what it is. I've never seen one that says "look, all this stuff is optional, write your software however, here's how to really get to grips with the domain model".
I don't think it's the critics conflating. It is what it is.
Every text I've ever written on DDD has made it pretty clear that these patterns are at the very heart of what it is. I've never seen one that says "look, all this stuff is optional, write your software however, here's how to really get to grips with the domain model".
I don't think it's the critics conflating. It is what it is.