fadarve1/prueba-tecnica

Purpose and Entry Points

OrderFlow is a small order-management system: a .NET 8 REST API backed by PostgreSQL and an Angular 22 standalone client for listing, filtering, creating, editing, and deleting orders. Backend startup is backend/src/OrderManagement.Api/Program.cs; frontend bootstrap is frontend/src/main.ts. Database schema initialization is supplied by 001_init.sql and started through docker-compose.yml.

Backend Layering and Dependency Boundary

The backend follows Clean Architecture. The Domain layer owns order entities and status semantics without infrastructure dependencies: backend/src/OrderManagement.Domain/Entities/Order.cs, backend/src/OrderManagement.Domain/Entities/OrderItem.cs, and backend/src/OrderManagement.Domain/Enums/OrderStatus.cs. The Application layer defines use-case contracts, DTO boundaries, and domain-facing exceptions, insulating service logic from EF Core/PostgreSQL.

API Transport Layer

MVC routes are concentrated in backend/src/OrderManagement.Api/Controllers/OrdersController.cs, exposing CRUD and filtered search under /api/orders. Requests map into application DTOs such as backend/src/OrderManagement.Application/DTOs/SaveOrderRequest.cs; responses use order DTOs. backend/src/OrderManagement.Api/Infrastructure/GlobalExceptionHandler.cs is the HTTP error boundary, translating application failures such as missing or duplicate orders into consistent API responses.

Order Use-Case Flow

backend/src/OrderManagement.Application/Services/OrderService.cs is the central orchestration stage for listing, reading, saving/updating, and deleting orders. It enforces application behavior and converts between domain entities and DTOs. It depends only on the persistence abstraction at backend/src/OrderManagement.Application/Abstractions/IOrderRepository.cs, not the concrete database implementation. Application-specific failure paths are represented by backend/src/OrderManagement.Application/Exceptions/OrderNotFoundException.cs and backend/src/OrderManagement.Application/Exceptions/DuplicateOrderNumberException.cs.

Persistence and Database

Infrastructure implements the Application repository contract in backend/src/OrderManagement.Infrastructure/Repositories/OrderRepository.cs. EF Core mapping and aggregate persistence are defined by backend/src/OrderManagement.Infrastructure/Persistence/OrderDbContext.cs, with entity configuration in backend/src/OrderManagement.Infrastructure/Persistence/Configurations/OrderConfiguration.cs and backend/src/OrderManagement.Infrastructure/Persistence/Configurations/OrderItemConfiguration.cs. Dependency registrations cross the composition boundary through backend/src/OrderManagement.Infrastructure/DependencyInjection.cs, invoked by API startup.

PostgreSQL 18 is the external state service. docker-compose.yml provisions it; 001_init.sql establishes its schema and database-side constraints/indexes/logic. The default connection can be overridden with ConnectionStrings__DefaultConnection.

Frontend Application Flow

The Angular client is a standalone SPA configured from frontend/src/app/app.config.ts and navigated through frontend/src/app/app.routes.ts. frontend/src/app/core/services/order.service.ts is the frontend/API boundary, using shared order models from frontend/src/app/core/models/order.model.ts to call the REST endpoints. UI feature components separate read and mutation workflows: frontend/src/app/features/orders/order-list.component.ts handles list/filter/delete behavior, while frontend/src/app/features/orders/order-form.component.ts handles create and edit submission.

Runtime Topology

The browser serves the Angular app on port 4200 and issues HTTP requests to the .NET API on port 5080. The API composes controllers, application services, and EF Core infrastructure, then connects to PostgreSQL on port 5432. Key deployment/runtime configuration is in backend/src/OrderManagement.Api/appsettings.json and docker-compose.yml.