title: Domain layer and DAO layer with DDD approach
body: <p>According to many programers, DAO layer can be bypassed when using JPA.</p>
  
  <p>While using DDD approach, domain layer composes of <strong>infrastructure region</strong> (containing external resources like repositories implementations) and <strong>domain region</strong> (with entities, needed value objects and repositories interfaces and services etc...).</p>
  
  <p>Thus, if DOA layer is skipped, should the infrastructure region be part of domain layer within a package called 'infrastructure' for instance ?</p>
  
  <p>If infrastructure part should be moved in a separated layer (separated project to get things cleaner), are circular dependencies acceptable between domain layer and infrastrure layer? Indeed, <strong>entities and interface repositories must be shared</strong>. </p>
  
  <p>Otherwise, should I separate entities and repositories interfaces from Domain layer in order to be considered as an independent thing shared by domain and infrastructure ?</p>
  
  <p>What is the good practice ?</p>