How er-engineer/finalproject works
This is a layered Northwind catalog and user-authentication application, exposed through an ASP.NET Web API. The main workflow is an API request routed to a business service, which applies product rules or authentication logic and uses data-access abstractions; product operations can also consult category counts. The tree includes EF and in-memory persistence, JWT support, and cross-cutting caching, validation, security, and interception. The README is empty, so unsampled capabilities and wiring are represented conservatively; dashed links mark relationships not established by the excerpts or source index.
Main entry points: ProductManager.cs Product service · AuthManager.cs Authentication service · Program.cs API host · CategoryManager.cs Category service
Components 22
API
- API host
WebAPI/Program.cs - Products API
WebAPI/Controllers/ProductsController.cs - Categories API
WebAPI/Controllers/CategoriesController.cs - Authentication API
WebAPI/Controllers/AuthController.cs
Business services
- Product service
Business/Concrete/ProductManager.cs - Category service
Business/Concrete/CategoryManager.cs - User service
Business/Concrete/UserManager.cs - Authentication service
Business/Concrete/AuthManager.cs - Product rules
Business/Concrete/ProductManager.cs
Data access
- Product data access
DataAccess/Abstract/IProductDal.cs - Category data access
DataAccess/Abstract/ICategoryDal.cs - User data access
DataAccess/Abstract/IUserDal.cs - Order and customer access
DataAccess/Abstract - EF adapters
DataAccess/Concrete/EntityFramework - In-memory products
DataAccess/Concrete/InMemory/InMemoryProductDal.cs - Northwind context
DataAccess/Concrete/EntityFramework/NorthwindContext.cs
Core infrastructure
- JWT token helper
Core/Utilities/Security/JWT/JwtHelper.cs - Password hashing
Core/Utilities/Security/Hashing/HashingHelper.cs - Memory cache
Core/CrossCuttingConcerns/Caching/Microsoft/MemoryCacheManager.cs - Validation aspects
Core/Aspects/Autofac/Validation - Result types
Core/Utilities/Results
Other components
- API client
Connections 26
- API client → Products API: requests
- API client → Categories API: requests
- API client → Authentication API: requests
- API host → Products API: hosts
- API host → Categories API: hosts
- API host → Authentication API: hosts
- API host → EF adapters: registers
- Products API → Product service: uses service
WebAPI/Controllers/ProductsController.cs - Categories API → Category service: uses service
WebAPI/Controllers/CategoriesController.cs - Authentication API → Authentication service: uses service
WebAPI/Controllers/AuthController.cs - Product service → Product data access: queries
Business/Concrete/ProductManager.cs - Product service → Category service: checks count
Business/Concrete/ProductManager.cs - Category service → Category data access: queries
Business/Concrete/CategoryManager.cs - Authentication service → User service: delegates to
Business/Concrete/AuthManager.cs - User service → User data access: queries
Business/Concrete/UserManager.cs - Authentication service → Password hashing: verifies password
Business/Concrete/AuthManager.cs - Authentication service → JWT token helper: creates token
Business/Concrete/AuthManager.cs - Product service → Product rules: checks rules
Business/Concrete/ProductManager.cs - Product service → Validation aspects: uses aspect
Business/Concrete/ProductManager.cs - Product service → Memory cache: caches results
- EF adapters → Northwind context: uses context
- In-memory products → Product data access: implements
- Order and customer access → Northwind context: uses context
- Product service → Result types: returns results
Business/Concrete/ProductManager.cs - Category service → Result types: returns results
Business/Concrete/CategoryManager.cs - Authentication service → Result types: returns results
Business/Concrete/AuthManager.cs