How sugrado/car-rental-dotnet works
Project Type and Purpose
This is a .NET-based N-tier architecture project implementing a daily car rental system with features like authentication, image management, and payment processing.
Main Architectural Components
• Presentation Layer (WebAPI)
• Business Layer
• Data Access Layer
• Core Layer (Infrastructure)
• Entities Layer
B. Cross-Cutting Concerns (Show as horizontal layers):
• Authentication/Authorization
• Caching
• Validation
• Exception Handling
• Logging
• Transaction Management
[Client Applications] → [WebAPI Layer]
• ↓
[Business Layer + Aspects]
• ↓
[Data Access Layer]
• ↓
[Database]
Important Relationships to Highlight
• JWT authentication flow
• Demonstrate the image upload process flow
• Rental process workflow
• Payment system integration
• Caching mechanism interaction
• Validation flow
Technical Elements
• Entity Framework Core
• Autofac IoC Container
• JWT Authentication
• Fluent Validation
• File Storage System
• Caching System
• Error Handling Middleware
Specific Implementation Details
• Synchronous operations
• Aspect interceptors
• Validation flows
• Authentication checks
• Database operations