Best Approach for Web Application using EF or not using EF?

Question

Hi All, I have a question in ASP .Net Web Application Whether Web Application should use Entity Framework or should not use Entity Framework? If there's a solution please let me know elaborately and what is the difference between these two...? As soon as possible. Thanks & Regards, Sourav

Amit Mohanty · Answer

Hey Sourav EF has advantages as well as disadvantages. Here I am describes about the benefits and limitations of entity framework. Advantages of Entity Framework: It provides auto generated code It reduce development time It reduce development cost It enables developers to visually design models and mapping of database It provides capability of programming a conceptual model. It provides unique syntax (LINQ / Yoda) for all object queries whether it is database or not It allow multiple conceptual models to mapped to a single storage schema. Disadvantages of Entity Framework: Lazy loading is the main drawbacks of EF Its logical schema is not able to understand business entities and relation among each other Logical schema of database is not capable of using certain parts of application It is not available for every RDMS Need to handle data in nontraditional way It does not work if we change any schema of the database. We need to update the schema on the solution. It is not good for huge domain model. In short we can say EF are good for small range of applications. But if we overcome the drawbacks of EF it will be perfect for any type of applications.

Jaimin Shethiya · Answer

Hello Saurav, If you application is small then you have to go-ahed whith EF but your application is large then you have not go-ahed with EF. you have to go-ahed Dapper ORM to your application. Dapper ORM is the fastest ORM to perform CRUD operation. here is the link how to use Dapper ORM. https://dapper-tutorial.net/dapper let me know if you have needed anything else. Thanks

Ramesh Palanivel · Answer

Hi Sourav, Entity Framework is ORM Framework and used to bind your dataset object directly into your DB Model. It reduces the code and easy to bind, But slower then Ado.net. To know more about Entity Framework, please refer below link https://www.entityframeworktutorial.net/what-is-entityframework.aspx ADO.net will return result as data set, you have to loop the dataset results to bind your Database model. Faster than Entity Framework, but need to write more code. If you want to use ORM with ADO.net, Go with Dapper Which is faster then Entity framework. Dapper will help you to use ADO.net code and it helps you to bind your dataset results to your DB Model class. Please let me know if you need any more clarifications.

Jaimin Shethiya · Answer

Hello Sourav, Yes because if EF used in our application side then we have maintain our application easily in coding side like relationship and other stuff, so most of the used that, and also EF provide to automatically created the SQL tables and modified table data. here is the fully knowledge describe EF, can you please checked once if you have a time. https://www.entityframeworktutorial.net/what-is-entityframework.aspx If we used Dapper ORM or other any ORM then in that case we have to maintain all things by coding.

Sourav Kumar Das · Answer

Hi Amit Mohanty , Ramesh Palanivel & Jaimin Shethiya I accept all your answers and I got clear knowledege of EF. Thanks & Regards, Sourav

Sourav Kumar Das · Answer

Hi All, Does this Enitiy Framework is been used at the emerging Industries?