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

Only adding to what others have already said; My personal experience is that people often end up with an anemic model and a single model instead of multiple context specific models.

Another problem is that many focus more on the infrastructure and patterns used in DDD. Just because you have entities and repositoriesand are using (n)Hibernate it doesn't mean you are doing DDD.