title: Is it good practice to have multiple data contexts?
body: <p>When breaking a solution out into multiple projects, does it make sense to have multiple data contexts or share the context?</p>
  
  <p>Example, for a web portal you have:</p>
  
  <pre><code>App.Service1
  App.Service2
  App.Web (references Service1 and Service2)
  </code></pre>
  
  <p>Now would you have it so that Service1 and Service2 share the same DataContext or they each have their own?</p>
  
  <p>Keep in mind that both <code>Service1</code> and <code>Service2</code> are both connecting to the exact same database, they are just seperated in order to keep things more isolated.</p>
  
  <p>I'm using EF6.</p>