title: Best practice to apply domain driven design in .NET?
body: <p>I have been trying to learn and apply domain driven concept into my software development. The first thing that I try to do is creating my domain model based on business logic needs. I often also use OR Mapping tool, such as LLBLGen, NHibernate, or Linq to SQL, to create data model and data access layer. The domain model and data model, however, are often very similar which make me wonder what benefit I really get by maintaining two models. </p>
  
  <p>Can someone share their practical thoughts about domain driven design? Furthermore, how would you deal with data model or data access layer when applying DDD in your application?</p>
  
  <p>Thanks in advance. </p>
  
  <p><strong>EDIT</strong></p>
  
  <p>Found a good <a href="https://web.archive.org/web/20110503184234/http://blogs.hibernatingrhinos.com/nhibernate/archive/2008/10/08/the-repository-pattern.aspx" rel="nofollow noreferrer">article</a>, with sample code, about Repository Pattern. </p>