title: Entity Framework: One Database, Multiple DbContexts. Is this a bad idea?
body: <p>My impression to date has been that a <code>DbContext</code> is meant to represent your database, and thus, if your application uses one database, you'd want only one <code>DbContext</code>.</p>
  
  <p>However, some colleagues want to break functional areas out into separate <code>DbContext</code> classes.</p>
  
  <p>I believe this comes from a good place -- a desire to keep the code cleaner -- but it seems volatile. My gut's telling me it's a bad idea, but unfortunately, my gut feeling is not a sufficient condition for a design decision.</p>
  
  <p>So I'm looking for:</p>
  
  <p>A) concrete examples of why this might be a bad idea;</p>
  
  <p>B) assurances that this will all work out just fine.</p>