A simple yet organized project template for building ASP.NET Core APIs using .NET Core 3.1 (the latest/fastest version of .NET Core to date) with preconfigured tools and frameworks. It features most of the functionalities that an API will have such as database CRUD operations, Token-based Authorization, Http Response format consistency, Global exception handling, Logging, Http Request rate limiting, HealthChecks and many more. The goal is to help you get up to speed when setting up the core structure of your app and its dependencies when spinning up a new ASP.NET Core API project. This enables you to focus on implementing business specific code requirements without you having to copy and paste the core structure of your project, common features, and installing its dependencies all over again. This will speed up your development time while enforcing standard project structure with its dependencies and configurations for all your apps.
If you are looking for a project template for ASP.NET Core API that you can reuse across your team, or if you are new to ASP.NET Core and would like to get up to speed on how it works without having you to configure most of the basic features that an API will have, then this is for you.
Keep in mind that you can always replace and choose whatever framework you want to use for your API. After all, the template is just a skeleton for your project structure with default preconfigured middlewares. For example, you can always replace Dapper with Entity Framework Core, PetaPoco, etc. and configure them yourself. You can also replace Serilog with whatever logging frameworks and providers you want that works with ASP.NET Core - the choice is yours.
Key Takeaways
Here's the list of the good stuff that you can get when using the template:
Configured Sample Code for database CRUD operations.
Configured Basic Data Access using Dapper.
Configured Logging using Serilog.
Configured AutoMapper for mapping entity models to DTOs.
Configured FluentValidation for DTO validations.
Configured AutoWrapper for handling request Exceptions and consistent HTTP response format.
Configured AutoWrapper.Server for unwrapping the Result attribute from AutoWrapper's ApiResponse output.
Configured Swagger API Documentation.
Configured CORS.
Configured JWT Authorization and Validation.
Configured Sample Code for Requesting Client Credentials Token.
Configured Swagger to secure API documentation with Bearer Authorization.
Configured Sample Code for connecting Protected External APIs.
Configured Sample Code for implementing custom API Pagination.
Configured HttpClient Resilience and Transient fault-handling.
Configured Http Request Rate Limiter.
Configured HealthChecks and HealthChecksUI.
Configured Unit Test Project with xUnit.
[Deprecated] Configured Sample Code for Worker service. For handling extensive process in the background, you may want to look at the Worker Template created by Jude Daryl Clarino. The template was also based on ApiBoilerPlate.
If you follow step 1, then you can skip this step and run the application right away.
If you have a different database and table name then you need to change the connectionString in appsettings.json that is pointing to the newly created database. You can get the connectionString values in the properties window of the "TestDB" database in Visual Studio.
Feel free to request an issue on github if you find bugs or request a new feature. Your valuable feedback is much appreciated to better improve this project. If you find this useful, please give it a star to show your support for this project.
请发表评论