How yildiraygemuk/logisticoperationapi works
Main Components
a. API Layer (Entry Point)
• LogisticCompany.API
• Controllers for different entities (Vehicle, Maintenance, User, etc.)
• Authentication/Authorization handling
b. Business Layer
• Business logic implementation
• Service interfaces and implementations
• AutoMapper profiles
• Validation aspects
c. Data Access Layer
• Entity Framework Core context
• Repositories
• Database configurations
• Migrations
d. Core Layer
• Cross-cutting concerns
• Security implementations
• Logging infrastructure
• Generic repository patterns
• Result patterns
e. Entity Layer
• Domain models
• DTOs
• View Models
[Mobile Clients] ←→ [Web Portal]
• ↓ ↓
• [API Gateway Layer]
• ↓
[Authentication/Authorization]
• ↓
• [Business Layer]
• ↓
• [Data Access Layer]
• ↓
• [Database Layer]
Component Relationships
• REST API calls between clients and API
• Service calls between layers
• Database operations
• Cross-cutting concern interactions
Specific Implementation Details
• JWT Authentication (shown in Core/Security)
• AutoFac Dependency Injection
• Entity Framework Core
• SeriLog implementation
• AutoMapper profiles
Additional Elements
• Maintenance workflow
• Vehicle management
• User management
• Reporting system
Technical Specifications
Annotations for:
• .NET 6.0 framework
• Entity Framework Core
• AutoFac
• JWT Authentication
• SeriLog
• AutoMapper
Cross-Cutting Concerns
Horizontal layers for:
• Exception handling
• Logging
• Validation
• Authentication
• Authorization
The scalable data access layer with Entity Framework Core
Remember to:
• Keep components loosely coupled
• Clear boundaries between layers
• Security boundaries
• Notes for important architectural decisions
This system design should reflect the project's focus on maintenance process management through mobile devices while providing comprehensive reporting capabilities through the web portal.