title: how to structure solution to allow for multiple data sources for a repository
body: <p><strong>How can I structure my solution in order to allow multiple data sources for the same repository?</strong></p>
  
  <p>I am currently reviewing the <a href="https://app.pluralsight.com/player?course=patterns-library&amp;author=scott-allen&amp;name=pattern-repository&amp;clip=7&amp;mode=live" rel="nofollow noreferrer">pluralsight course</a>: </p>
  
  <p><a href="https://app.pluralsight.com/player?course=patterns-library&amp;author=scott-allen&amp;name=pattern-repository&amp;clip=7&amp;mode=live" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/quEYp.png" alt="enter image description here"></a></p>
  
  <p>My <code>employee</code> entity has multiple data sources, such as a sql server database as well as a CRM instance. </p>
  
  <p><strong>Does the repository pattern allow for multiple data sources for the same repository?</strong></p>
  
  <p>In my case, I would like to abstract the repository access to the Employee entity by wrapping an Employee repository around it, but I am not sure if I'm implementing an anti-pattern by requiring multiple data sources for the same repository. </p>