How boubsila/webproject2025 works
Project type and purpose
• This is a full-stack online marketplace (“Art Marketplace Platform”) where artisan sellers, customers, delivery partners and administrators each have a dedicated dashboard.
• Front-end: Angular SPA.
• Back-end: ASP.NET Core REST API with N-tier layered architecture (Presentation → Business → Data → Domain).
• Persists data via Entity Framework Core to a relational database.
• Secured by JWT token authentication.
File structure
• Top-level directories:
• Frontend: Angular project under /Frontend/frontend_artisans.
• Backend: ASP.NET solution under /Backend/Backend_Artisans with four sub-projects:
– Domain: entity definitions and DTOs
– Data: EF Core DbContext, migrations, repository implementation
– Business: service interfaces and implementations
– Backend_Artisans: API controllers, authentication service, Program.cs, appsettings
• Notice typical MVC/RESTful API controllers in Backend_Artisans/Controllers.
• Database migration files in Data/Migrations.
• Angular modules in src/app (Auth, Dashboard per role, NavBar, Services).
• Configuration files: angular.json, tsconfig.json, appsettings.json, launchSettings.json.
README for insights
• Confirms tech stack: Angular + ASP.NET Core + EF Core + JWT.
• Lists user roles and use cases: Artisan, Client, Delivery partner, Admin.
• Shows example API endpoints for each role.
• Describes N-tier REST architecture.
a. Main components
• Users (Artisan, Client, Delivery, Admin)
• Angular SPA (Presentation layer)
• ASP.NET Core API (Presentation → Controllers)
• Business Logic layer (IService, Service)
• Data Access layer (DbContext, IRepo, Repo)
• Domain Model (Entities, DTOs)
• Relational Database (SQL Server)
• Authentication Service (JWT token provider/validator)
b. Relationships & interactions
• Users → HTTP(S) calls → Angular SPA
• Angular services call REST endpoints on ASP.NET Core API
• Controllers inject Business services → call Data repositories → query/update DB
• Authentication: login/register endpoints issue JWT; Angular interceptor attaches token; API middleware validates token
c. Architectural patterns & design principles
• Layered (N-tier) architecture: Presentation, Application (Controllers), Domain, Business, Infrastructure (Data)
• RESTful API design
• Dependency Injection for services and repositories
• JWT-based stateless authentication
• Separation of concerns (Angular modules per feature, .NET projects per layer)
d. Key technologies/frameworks
• Angular (TypeScript, RxJS, Guards, Interceptors)
• ASP.NET Core (Controllers, Middleware, DI)
• Entity Framework Core (Code-first migrations)
• JWT tokens for auth