misael-jk/pizzaria-tp

Purpose and entry point

This is a .NET pizzeria backend organized as a layered solution: HTTP API, business services, domain model/contracts, and persistence. The runtime entry point is src/Pizzeria/API/Program.cs; the solution root is src/Pizzeria/Pizzeria.sln.

HTTP API boundary

Minimal/API endpoint modules expose operations for customers, pizzas, and orders. They accept request DTOs and delegate to services rather than accessing repositories directly.

• src/Pizzeria/API/Endpoints/ClienteEndpoints.cs

• src/Pizzeria/API/Endpoints/PizzaEndpoints.cs

• src/Pizzeria/API/Endpoints/PedidoEndpoints.cs

• src/Pizzeria/API/DTO/CearPedidoDto.cs

• src/Pizzeria/API/DTO/DetalleDto.cs

Domain model

The domain layer defines the central business records: customers, pizza catalog entries, orders, and order-line details. Order lifecycle state is represented separately by an enum.

• src/Pizzeria/Dominio/Entidades/Cliente.cs

• src/Pizzeria/Dominio/Entidades/Pizza.cs

• src/Pizzeria/Dominio/Entidades/Pedido.cs

• src/Pizzeria/Dominio/Entidades/DetallePedido.cs

• src/Pizzeria/Dominio/Enums/EstadoPedido.cs

Service/application layer

Services implement use-case orchestration between API-facing operations and repository contracts. The order service is the key transaction/business-flow boundary: it likely coordinates customer lookup, pizza/detail handling, order creation, and state handling.

• src/Pizzeria/Servicios/Service/ClienteService.cs

• src/Pizzeria/Servicios/Service/PizzaService.cs

• src/Pizzeria/Servicios/Service/PedidoService.cs

• src/Pizzeria/Servicios/Interface/IPedidoService.cs

Persistence abstraction and implementations

The domain owns repository interfaces, keeping storage concerns outside the domain. Persistence supplies concrete repositories, with RepoBase providing shared database access behavior.

• src/Pizzeria/Dominio/Interfaces/IClienteRepository.cs

• src/Pizzeria/Dominio/Interfaces/IPizzaRepository.cs

• src/Pizzeria/Dominio/Interfaces/IPedidoRepository.cs

• src/Pizzeria/Persistencia/RepoBase.cs

• src/Pizzeria/Persistencia/Repos/PedidoRepository.cs

Primary flow and boundaries

A request flows from an endpoint to its service interface/implementation, then through a domain repository interface to a persistence repository and database. Results return through the same layers. DTOs form the HTTP input boundary; domain entities form the core business/storage model; repository interfaces form the dependency-inversion boundary between services/domain and persistence.

Database and infrastructure

Database structure and seed/sample data are maintained as SQL artifacts, external to the .NET projects:

• DataBase/schema.sql

• DataBase/inserts.sql

The API has development runtime configuration in src/Pizzeria/API/appsettings.Development.json and launch profiles in src/Pizzeria/API/Properties/launchSettings.json. No frontend, message broker, or external third-party service integration is evident from the repository tree.