title: Repository Pattern and multiple related core entities or business objects - one repository or more?
body: <p>I am looking at implementing the repository pattern (since what I came up with was 90% an implementation of it anyway), and have come across a design question - where I have two or more core business objects (for example, Business and Contact in a CRM app), the BO's can be strongly related or not related at all.</p>
  
  <p>In this situation, should I implement one repository (CrmRepository for example, with .addBusiness(), .addContact() et al), or multiple repositories (BusinessRepository, ContactRepository each with their own .add(), .delete() et al).</p>
  
  <p>What is the best practice in this situation?</p>
  
  <p>The underlying DAL is EF4.</p>
  
  <p>Regards</p>
  
  <p>Moo</p>