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

One of the biggest pitfalls is that you end up with a so-called anemic model where your entities are primarily only data bearing and contain no business logic. This situation often arises when you build your domain model on top of an existing relational data model and just make each table in the database an entity in your domain model.