title: How to design Data Access layer in Entity Framework (Data First)
body: <p>I am working on an enterprise solutions and we are using EF data first for our data access layer. Currently we have around 100 tables in database and we are adding them to one Entity data model. As project will grow we are going to have one big entity data model with around 500 tables.</p>
  
  <p>We are planning to create small modules for each component of application and creating separate entity data model for each.If somebody has experience of this approach then Please share pros and cons of it.</p>