Domain-driven-design (DDD) pitfalls

Question

I am quite new with DDD and would like to know about any pitfalls you might want to share. I will summarize it later for more newbies to read :)

Thanks

Summary s

Answer 1

Beware of the Big Ball of Mud.

One of the pitfalls of domain driven design is to introduce ambiguity into a model. As explained in the article Strategic Domain Driven Design with Context Mapping:

Ambiguity is the super-villain of our Ubiquitous Language

This may happen when two distinct concepts share the same name, or when the same concept can have different uses. It may be necessary to

expose the domain structure in terms of bounded contexts in a context map

If a model is used in too many different ways, or has too many responsibilities, it may be a sign that it should be divided.