title: anemic domain model versus domain model
body: <p>Being confused again after reading about this anti-pattern and the many concerns about it here on SO.</p>
  
  <p>If I have a domain model and capture the data that must be persisted in a data transfer object, does that make my domain model a wrapper around the data? In that case I would be using an anemic domain model. But if I add enough domain logic on that wrapper, at what point does it become a real domain model then?</p>
  
  <p>I get the impression that capturing what must be persisted in a domain model violates good practice and creates the anemic domain model anti-pattern. Yet if you use a relational DB there's no way to avoid to single out the part that makes the state of the object and save it.</p>
  
  <p>Since I'm pretty confused about the concepts I'm not sure that what I write makes sense. Feel free to ask clarification.</p>