EF Core 与 ADO.NET

Question

One of my customer is developing a set of ASP.NET Core API's which has to support 15,00,000 requests per hour.

All the request will end up interacting with SQL Server tables. Some are SQL Server In-Memory OLTP tables.

The customer is currently using ADO.Net and Stored Procedures to make SQL connectivity in similar application and wondering if they continue using the same or should consider EF Core.

I myself have mostly used ADO.Net in past so wanted to check if we can suggest EF Core here or sticking to ADO.Net with SP is the safest bet?

I know that ADO.NET is the safest choice if you are committed to using Stored Procedures and have a extreme performance requirements, but EF is still relevant in the market and is being used by many. If it was actually so bad it would surely have had an alternative or would have been scrapped.

So is ADO.NET safe bet or we can move on with new technological advancements like EF Core as an ORM and use it with LINQ functionalities, writing less code etc.?

Answer 1

What to do?

is ADO.NET safe bet or we can move on with new technological advancements like EF Core as an ORM and use it with LINQ functionalities, writing less code etc.?

We cannot make a decision based on one stat (15,000,000), but one option is to migrate/extend with an ORM part by part. You can maintain existing code and add new functionality using an ORM. As you gain experience you can make better decision.

---

or should consider EF Core

I suppose one should always consider available contemporary technologies upon starting a significant piece of work but it would be irresponsible to say that all new projects should be written in [insert_some_framework_here].

EF Core and stored procs

The following executes a stored procedure in EF Core.

var blogs = context.Blogs
    .FromSqlRaw("EXECUTE dbo.GetMostPopularBlogs")
    .ToList();

Please note that:

• it can be mixed and matched it with Linq queries
• there are limitations

Please see Raw SQL Queries .

---

Dapper and stored procs

Have you considered Dapper ? The following is directly from its official repo.

Dapper fully supports stored procs:

 var user = cnn.Query<User>("spGetUser", new {Id = 1}, commandType: CommandType.StoredProcedure).SingleOrDefault();

If you want something more fancy, you can do:

 var p = new DynamicParameters(); p.Add("@a", 11); p.Add("@b", dbType: DbType.Int32, direction: ParameterDirection.Output); p.Add("@c", dbType: DbType.Int32, direction: ParameterDirection.ReturnValue); cnn.Execute("spMagicProc", p, commandType: CommandType.StoredProcedure); int b = p.Get<int>("@b"); int c = p.Get<int>("@c");