title: Repository vs Service pattern in DAL: EF and Dapper
body: <p>I'm working on project and I need to design the DAL. I will be using <code>Entity Framework</code> for most of the project and <code>Dapper</code> for some performance-sensitive areas. </p>
  
  <p>I was thinking about using the Repository pattern but then EF already implements this pattern in some sense. But that's not the case with Dapper. Then I am wondering is it valid to mix Repository and Service patterns in my DAL? Or would this be crossing into the Business Logic Layer?</p>
  
  <p>A sample structure I was thinking to buid:</p>
  
  <pre><code>MyProjectName.Main
      Views/
      Controllers/
      Infrastructure/
      ...
  MyProjectName.DAL
      DataService.EF/
          fileName.cs
          ...
      DataService.Dapper/
          fileName.cs
          ...
  </code></pre>