title: domain driven design using Entity framework 4
body: <p>I have read some posts which discuss about how to use EF entities as business objects </p>
  
  <p><a href="https://stackoverflow.com/questions/217655/using-entity-framework-entities-as-business-objects">Using Entity Framework entities as business objects?</a></p>
  
  <p>but doesn't this make the design of the business objects dependent on the data model? Is this the right practice for enterprise applications? shouldn't the domain and data model be independent and changes in one shouldn't affect the other? if I choose to keep them separate, then do I need to create another layer to populate the business objects from the EF entities? if I have both custom business objects and the EF entities, which one is used to transfer data between layers (including all the way to UI)? is there an architectural pattern for this? It would be useful if there is a sample application that demonstrates these concepts (not simply a demo version, suitable to use in an enterprise application).</p>
  
  <p>This link explains the problem clearly</p>
  
  <p><a href="http://msdn.microsoft.com/en-us/magazine/dd882510.aspx#id0420099" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/magazine/dd882510.aspx#id0420099</a></p>