Entity Framework vs Dapper

Question

Please let me know which is better dapper or entity framework. I have checked the Dapper code I do not understand it.

Rijwan Ansari · Answer

Entity Framework (EF) and Dapper both are object-relational mappers that enable .NET developers to work with relational data using domain-specific objects. Dapper owns the title of King of Micro ORM in terms of performance. Entityframework is quite rich and easy to use. However, dapper has performance improved. Sometime, we use both ORMs in same solution. EF for normal operations and Dapper for reports, long or complex queries. Entity Framework Advantages Entity Framework allows you to create a model by writing code or using boxes and lines in the EF Designer and generate a new database. You can write code against the Entity Framework, and the system will automatically produce objects for you as well as track changes on those objects and simplify the process of updating the database. One common syntax (LINQ) for all object queries whether it is a database or not and pretty fast if used as intended, easy to implement and less coding required to accomplish complex tasks. The EF can replace a large chunk of code you would otherwise have to write and maintain yourself. It provides auto-generated code It reduces development time and cost. It enables developers to visually design models and mapping of database Disadvantages You have to think in a non-traditional way of handling data, not available for every database. If there is any schema change in database FE won't work and you have to update the schema in solution as well. The EF queries are generated by the provider that we cannot control. It is not good for a huge domain model. Lazy loading is the main drawbacks of EF Dapper Advantages Dapper make it easy to correctly parameterize queries It can easily execute queries (scalar, multi-rows, multi-grids, and no-results) Make it easy to turn results into objects It is very efficient and owns the title of King of Micro ORM in terms of performance. Disadvantages Dapper can't generate a class model for you It cannot generate queries for you It cannot track objects and their changes The raw dapper library doesn't provide CRUD features, but the "contrib" additional package does provide basic CRUD.

Kirtesh Shah · Answer

Hi Rohan, It is depent on your requirement. Below are few important points help you to decide, 1. If you need full-fledged ORM with lots of cool features, including change tracking then go with EF. Despite the fact that Dapper isn't really an ORM at all; it's more of a mapper library designed to map data results to C# objects. 2. if need to do simple ORM thing then go with Dapper. because Drapper is faster then EF. Dapper is light weight. Dapper was built with performance and ease of use in mind. It provides support for both static and dynamic object binding using transactions, stored procedures, or bulk inserts of data. 3. As Dapper does very basic job, it is faster; but you have to write more code. As EF does much more than that, it is (bit) slower; but you have to write less code. Thanks

Jishan Siddique · Answer

You can check this question -> Dapper VS EF https://www.c-sharpcorner.com/interview-question/what-is-difference-between-entity-framework-and-dapper Dapper In the dapper, Model class you need to create as per the table. It can execute queries like an example (Scalar/Multi rows select, and Insert/Update/Delete) In the dapper, you can create a query as per you're requirement and run the query with and without parameters. Entity Frameworks In EF, Based on the table model class will be created. In EF, EF provides the auto-generated code like EDMX, Text-template files. In EF, It reduces the development times like you can use the ready method instead of Select query you can directly use modelobjects.ToList() -> select query prepared in the background and the result will be mapped into the model. In EF, you can show generated queries. Note: Recently I've created on the blog you can check this also How Dapper Has Become King ORM In C#/MVC/.NET/.CORE https://www.c-sharpcorner.com/blogs/how-dapper-become-king-orm-in-c-sharpmvcnetcore But if you are planning to go with EF then please go for it but EF 6 here you can find all details related to EF-6 EF-6 https://docs.microsoft.com/en-us/ef/ef6/

Kirtesh Shah · Answer

Hi, Check this it will help you, https://entityframework.net/ef-vs-dapper Thanks

Rohan · Answer

Rijwan Ansari - So what is best .

Rohan · Answer

Jishan Siddique - Please let me which is better ?