title: DDD - Persistence Model and Domain Model
body: <p>I am trying to learn domain-driven design (DDD), and I think I got the basic idea. But there is something confusing me.</p>
  
  <p>In DDD, are the persistence model and domain model different things? I mean, we design our domain and classes with only domain concerns in mind; that's okay. But after that when we are building our repositories or any other data persistence system, should we create another representation of our model to use in persistence layer?</p>
  
  <p>I was thinking our domain model is used in persistence too, meaning our repositories return our domain objects from queries. But today, I read this post, and I'm a little confused:</p>
  
  <p><em><a href="https://blog.sapiensworks.com/post/2012/04/07/Just-Stop-It!-The-Domain-Model-Is-Not-The-Persistence-Model.aspx" rel="noreferrer">Just Stop It! The Domain Model Is Not The Persistence Model</a></em></p>
  
  <p>If that's true what would be the advantage of having separate persistence objects from domain objects?</p>