How ysgstudyhards/fastframework works
Project type and purpose
• This is a .NET-based rapid development framework (“FastFramework”) plus a sample platform implementation (“DotNetGuideBlog”).
• It’s a layered, full-stack solution: core libraries, shared utilities, and a sample multi-layer web API (DAL, BLL, Repository, Model, WebAPI). It integrates authentication/authorization (JWT, RBAC), data access (EF Core, Dapper), DI (Autofac), logging (Serilog → ELK), caching (Redis), scheduling (Quartz.NET), and a front-end (uni-app/Vben Admin).
File structure
• Top-level:
• Core/FastFramework.Core → framework’s core services, abstractions, interfaces
• Shared/FastFramework.Shared → common DTOs, constants, shared helpers
• Platforms/DotNetGuideBlog → sample platform with subprojects:
– DotNetGuideBlogModel (entity definitions)
– DotNetGuideBlogDAL (EF Core + Dapper data context & migrations)
– DotNetGuideBlogRepository (repository implementations)
– DotNetGuideBlogBLL (business logic layer, service interfaces + implementations)
– DotNetGuideBlogWebAPI (ASP.NET Core Web API exposing HTTP endpoints)
• FastFramework.sln ties them all together
README insights
• Confirms .NET 8 stack, integrated modules (RBAC, JWT, logging, ELK, config center), plus recommended front-end tech (uni-app, Vben Admin).
Detail
• Middleware pipeline: Authentication → Logging → Rate Limit → Routing.
• Both EF Core and Dapper flows to the database.
• Background job scheduler (Quartz) calling into BLL.