Scope of this project is to analyze different .NET approaches to retrieve data from MSSQL database and expose through a Web Api Rest. For semplicity only Get method will be considered but interaction with database will use different ways and different technologies:

1. EntityFrameworkCore 2.1
2. EntityFrameworkCore 3.1
3. EntityFrameworkCore 5.0
4. EntityFrameworkCore 6.0
5. Dapper (.Net 6.0) [info]
6. JsonPath (.Net 6.0) [info]

The database project contains just one table with five fields:

CREATE TABLE [dbo].[portfolio] (`
    [PortfolioId]     INT            NOT NULL,
    [PortfolioCode]   NVARCHAR (100) NOT NULL,
    [PortfolioName]   NVARCHAR (100) NOT NULL,
    [PortfolioType]   NVARCHAR (100) NOT NULL,
    [PortfolioStatus] NVARCHAR (100) NOT NULL
);

The table contains 20,000 rows.

The solution contains six projects for each technology plus a database project. All Web Api projects have the same structure:

1. Controller contains the controller
2. Models contains class that maps the database table
3. Services contains the repository patter
4. MyContext is the database context

1. Add Microsoft.EntityFrameworkCore by NuGet package to your project.
2. Update ConfigureServices in Startup class.
3. Create your model, Portfolio class, ensuring you will add a primary key.
4. Create your own context, MyContext class, inherited from DbContext where you set your data set. This class will use your model.
5. Create your repository class by injecting your context class. This class will have only one method, * GetPortfolios()*.
6. Creat your resourse in PortfolioController.

1. Add Dapper by NuGet package to your project.
2. Create your model, Portfolio class.
3. Create your resourse in PortfolioController.

1. Create your resourse in PortfolioController. It is only needed to pass the query you need. That's all.

The benchmark results are here proposed in two ways. One is by using a tool I created for Http Get requests Benchmark Rest and another one is by using Crank. Let's see.

Benchmark Rest has been used in a console by using these parameters:

1. Web Api url
2. number of iterations
3. method

The cumulative values have been calulated on a total of 5000 iterations for each method of the resource. The table contains 20,0000 rows.

Graph result of average respone time for Get, Post, Put, Delete

By using Crank (here you can find a guide) you do not need to launch the project but just setting it in a .yml file and you can run it locally. These the results:

... and finally the trace screenshots created in the crank job:

Type	Trace results
EF 3.1
EF 5.0
EF 6.0
Dapper (.NET 6.0)
JsonPath (.NET 6.0)