Last post Aug 10, 2014 01:49 AM by MetalAsp.Net
Aug 05, 2014 07:30 AM|shahbaz512|LINK
need some advise on a suitable approach to create a DAL for a new MVC project with existing database.
1- should a project have only ONE EF model no matter how many tables? wouldn't that affect the performance.
2- is it OK if we create multiple EF models based on different application modules, e.g. AccountingEFModel, HumanResourceEFModel, ContactsEFModel etc.
3- we may not be using MVC scaffolding, or binding features. so if we create HTML based forms and use jQuery Ajax/JASON, is EF a suitable DAL for handling data without any issues in future.
just wanna make a right decision before i start developing.
would appreciate your input, Cheers.
Aug 05, 2014 10:56 PM|Pengzhen Song - MSFT|LINK
About EF entity model, In general we should start thinking about breaking up a model when it has reached 50-100 entities. For more information, you can refer to the document:
#Working With Large Models In Entity Framework
#Working With Large Models In Entity Framework – Part 2
And I suggest that you use EF which can good meet our needs.
Aug 10, 2014 01:49 AM|MetalAsp.Net|LINK
Is this general rule still valid today? I ask because six years later (the article is from nov 2008) maybe entity framework has been improved/optimized to handle larger models? I'd be interested in your answer...