4 ms·
> DDD has little to say about the most crucial aspect of those boundaries - where the boundaries go and why. The whole point of DDD is that there can't be a on
by blowski 4y ago
> DDD has little to say about the most crucial aspect of those boundaries - where the boundaries go and why.
The whole point of DDD is that there can't be a one-size-fits-all answer to these questions. Instead, they give you some questions you need to think about, and tools that might help you find answers.
- pydry 4y agoThe whole point appears to be that there IS a one size fits all set of design patterns once you've got the right "bounded contexts" and the right "ubiquitous language". It doesn't have anything interesting to say about either one of those things though. The whole idea appears to be a set up for a bunch of design patterns.
- blowski 4y agoThere is definitely a part of the DDD community that wants to do it that way. I call it “domain driven design driven design”. But the big names in DDD have all explicitly said that’s wrong.