Is there any alternative for ADO.net & EFW?

Ravi Kiran Chanduri

I have been working on ADO.net majorly and on EFW for sometime on one project. I am going to Work on a new project and getting confused on choosing the DB layer. I have read some articles on performance of ADO.net and EFW. EFW is slower than ADO. So, I would like to choose the best one for my project. I know that, ADO.net implementation requires write more code. So, I am looking for more performance and less coding. Please suggest me for the alternative to ADO.net and EFW if exists, if not please suggest the best one between them.

Little info on project:

Project description: its going to be a single page application and data will be saved for a user on date wise. Need to fetch the data for the selected date.

IDE : VS2017 Framework: Latest version of the framework. Database: MS Sqlserver 2014 Service layer: WebAPi UI : Angular 6 with typescript.

Thanks in advanced.

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Sanwar Ranwa8y ago
Hi Ravi

Many ORM Available for .net

Each own has its own advantage and disadvantage. And it is purely depends on your requirement too. Get your hand wet that would be the best way to choose one.

For you project i recommended you to use Ado.net

Use Repository pattern

Ef reduce you development time speed wise its slow

You also use Dapper

I Share some links which help you for Question

https://weblogs.asp.net/fbouma/fetch-performance-of-various-net-orm-data-access-frameworks

http://www.techdreams.org/microsoft/aspnet/list-of-orm-libraries-available-for-net-and-the-best-one/7891-20120418
Ravi Kiran Chanduri8y ago
Thanks Divyng for tsparing time to reply my question with valuable information.

I said need to write more code for ADO for following reasons ,

I have to use the result in sending the http response through my Web API, So I need the data in serializable object. For that Ive to create the entity class

convert the result into that entity class type using any generic method by handing the conditions.

And regarding the suggestion on using Dapper , I didn't check that before. I will have a look.
Divyang Desai8y ago
It is not necessary to write more code for ADO.NET if you create your architecture in that way. I have created one architecture for internal project, which is fully using ADO.NET with less code, but in that case you have to work with generics and following one common pattern for all your DB methods.

Use of any ORM loose the performance of the application, so choosing EF or any other ORM is not a good idea especially when you expect huge traffic on your application.

However, sometimes we have to choose any ORM for faster development or any other reason. In that case I would suggest you to use Dapper (developed by Stack Exchange: https://github.com/StackExchange/Dapper) .

Dapper is slower then ADO.NET and faster then EF.