search

Hasanaltan-cpu / DataAccessRepo

In this project, we use data access tools as an Entity Framework.Initally you see definition of ORM then why we use EntityFramework then i will show some linq methods for database searches.In addition to that i will use Northwind database on SQL by using EntityFramework by DatabaseFirst approach & by CodeFirst approach.In a conclusion,i create a Phone Index For CRUD processes.
MIT License
6 stars 0 forks source link

Dapper vs Entity Framework #2

Open Burakkylmz opened 3 years ago

Burakkylmz commented 3 years ago

In this repository, you have made applications in the light of theoretical information about Entity Framework and its technologies. Some say that Dapper implementing ORM architecture is better. What do you think?

Burakkylmz commented 3 years ago

Do you have any information About Dapper?

Hasanaltan-cpu commented 3 years ago

Dapper is the micro library by ADO.NET.It is smaller than Entity Framework also it is more usefull than Entity Framework in terms of usage speed.Because of query that is sent from Dapper connected ADO.Net without any mutable.

Advantages of Dapper; 1.Performance in terms of speed; 2.Easily execute for queries and to bind object; 3.Dapper is Open Source library that's why you can check on the Git. Disadvantages of Dapper; 1.It is suitable for the code failure because of online written queries.Besides that you can see that failure on the run-time not the build-time; 2.Dapper doesn't create entity models for connecting the tables that we created; 3.Dapper doesn't create classes for you entities; 4.Dapper has not library that to generate queries; 5.All queries,you should write yourself by manuel; 6.Dapper doesn't follow entity objects situations; 7.That a object has been changed,dapper did not know that,i mean you should follow your entity objects manuelly.