This project is MVP WebAPI that do CRUD operations over Northwind database
Backend interacts with external world using RESTful, thus for every entity from database there are HTTP verbs through which you can add, update, delete, and read data.
This project uses such techniques as UnitOfWork and QueryProcessors. In particular UnitOfWork used to make abstraction from database server and QueryProcessor extract data from database. Another technique that I have used is middleware which passes default page size of pagination to the controller.
In this project I have faced problem of slow GET-verb response for some entities that have many records in database. I have solved this problem using two techniques:
- Caching;
- Pagination;
Caching helped me to optimize all GET requests but with help of pagination request become even faster. I am sure that you questioning yourself how I have dealt with problem of cache invalidation and saving state of pagination in order to make "give next page"/"give previous page" action. You can find answers to this question in my repository :)
- Platform -
ASP .NET Core 6.0 - Documentation -
Swagger - Programming Language -
C# - Data storage -
SQL Server 2017 - Data Access -
Entity Framework Core - Dependecy injection -
Native ASP.NET Core IOC container - Object mapping -
AutoMapper - Logging -
Default ASP .NET Core Logging - Unit testing -
xUnit,Moq,FluentAssertion - Caching -
Microsoft Caching