CODEWITHSUNDEEP
architecturedomain-driven-design
ken
ken

Reputation: 3745

Abusing domain driven design

How can people abuse of Domain Driven Design ? too much too little information in the domain, what would you consider an abuse? In your design experience did you run into any situation that you considered that the design is just too much ?

-Ken

Upvotes: 2

Views: 471

Answers (4)

Mathieson
Mathieson

Reputation: 1948

Evans own book talks about when it's not appropriate - if you're doing a small one screen application, that won't be extended in the future, then going to the trouble to construct an extensible DDD for that application is polishing the brass on the Titanic.

Upvotes: 0

Szymon Pobiega
Szymon Pobiega

Reputation: 3376

Abusing DDD is using DDD to build each and every system. Both soft (ubiquitous language, customer cooperation) and hard (design patterns) aspects of DDD can be abused.

Upvotes: 2

Adrian K
Adrian K

Reputation: 10227

I agree with Shiraz. Also:

  • By following the buzz-words and not following the underlying intent / principles.
  • When those doing the DDD don't accept feedback - as the teams overall understanding of the system matures they don't mature with it.
  • When the level of detail and the sheer size of the documentation becomes too unwieldly.
  • When things that should be re-used aren't - you end up with duplication that makes it harder to maintain a clear model.

Upvotes: 5

Shiraz Bhaiji
Shiraz Bhaiji

Reputation: 65471

You have analysis paralysis, where people analysis and design systems, but never actually build anything.

Upvotes: 5

Related Questions