How ammaryasser88/smartstoreapi works
Main Components
• API Layer (SmartStoreAPi)
• Application Layer (SmartStore.Application)
• Domain Layer (SmartStore.Domain)
• Shared Library (SmartStore.Shared)
• Database (SQL Server)
• External Clients (Web/Mobile frontends, POS devices)
• External Services (JWT Authentication, Logging, Email/SMS via MessageService)
Relationships & Data Flows
• Clients → HTTP requests → API Layer
• API Controllers ←→ Application Services
• Services ←→ UnitOfWork → Generic Repositories
• Repositories ←→ EF Core DbContext (SmartStoreContext) ←→ SQL Server
• AutoMapper & FluentValidation operate within the Application Layer to map DTOs and validate incoming data.
• Shared Library provides pagination utilities to both API and Application layers.
Architectural Patterns & Principles
• Clean Architecture: strict layer boundaries, dependency inversion (inner layers know nothing of outer layers)
• Repository Pattern + Unit of Work for data access abstraction
• DTO mapping via AutoMapper profiles
• Validation via FluentValidation validators
• Layered .NET projects grouped by responsibility (Application, Domain, API, Shared)
Technologies
• ASP.NET Core 8 (Web API)
• Entity Framework Core (ORM)
• SQL Server (Relational Database)
• AutoMapper (Object–Object Mapping)
• FluentValidation (Request Validation)
• JWT (Authentication)
Elements
• API Layer: Controllers, ConfigureServicesExtension, Program.cs
• Application Layer:
• BusinessServices & ApplicationServices interfaces & implementations
• GenericRepository, UnitOfWork
• AutoMapper Profiles & Validators
• Domain Layer: Entities, Configurations, DbContext, Migrations, Request/Response DTOs
• Shared Library: PaginationHelper & PaginationObject
• Database: SQL Server instance
• External Clients & Services: Web/Mobile, JWT Auth, MessageService