How leopuentearce-boop/restaurant-platform works
The README characterizes the repository as a foundation phase with no functional business modules, but the supplied tree and source excerpts show implemented REST workflows for restaurant operations. This map describes those evidenced backend capabilities; service internals not sampled are represented only where the tree identifies their modules.
Main entry points: PedidoController.java Orders API · AtencionController.java Service API · ReservaController.java Reservations API · CobroController.java Payments API
Components 25
REST API
- Orders API
restaurant-api/src/main/java/com/restaurant/api/ordering/api/controller/PedidoController.java - Service API
restaurant-api/src/main/java/com/restaurant/api/serviceoperation/api/controller/AtencionController.java - Reservations API
restaurant-api/src/main/java/com/restaurant/api/reservation/api/controller/ReservaController.java - Payments API
restaurant-api/src/main/java/com/restaurant/api/payment/api/controller/CobroController.java - Closing API
restaurant-api/src/main/java/com/restaurant/api/closing/api/controller/CierreController.java - Incidents API
restaurant-api/src/main/java/com/restaurant/api/incident/api/controller/IncidenciaController.java - Availability API
restaurant-api/src/main/java/com/restaurant/api/productavailability/api/controller/DisponibilidadProductoController.java - Public info API
restaurant-api/src/main/java/com/restaurant/api/publicinformation/api/controller/InformacionPublicaController.java
Restaurant Operations
- Order service
restaurant-api/src/main/java/com/restaurant/api/ordering/application/PedidoService.java - Service operation
restaurant-api/src/main/java/com/restaurant/api/serviceoperation/application/AtencionService.java - Reservation service
restaurant-api/src/main/java/com/restaurant/api/reservation/application/ReservaService.java - Payment service
restaurant-api/src/main/java/com/restaurant/api/payment/application/CobroService.java - Closing service
restaurant-api/src/main/java/com/restaurant/api/closing/application/CierreService.java - Incident service
restaurant-api/src/main/java/com/restaurant/api/incident/application/IncidenciaService.java - Availability service
restaurant-api/src/main/java/com/restaurant/api/productavailability/application/DisponibilidadProductoService.java - Public info service
restaurant-api/src/main/java/com/restaurant/api/publicinformation/application/InformacionPublicaService.java
Shared Domain
- Order repository
restaurant-api/src/main/java/com/restaurant/api/domain/repository/PedidoRepository.java - Service repository
restaurant-api/src/main/java/com/restaurant/api/domain/repository/AtencionRepository.java - Reservation repository
restaurant-api/src/main/java/com/restaurant/api/domain/repository/ReservaRepository.java - Payment repository
restaurant-api/src/main/java/com/restaurant/api/domain/repository/CobroRepository.java - Closing repository
restaurant-api/src/main/java/com/restaurant/api/domain/repository/CierreOperativoRepository.java - Incident repository
restaurant-api/src/main/java/com/restaurant/api/domain/repository/IncidenciaOperativaRepository.java - Availability repository
restaurant-api/src/main/java/com/restaurant/api/domain/repository/DisponibilidadProductoRepository.java - Public info repository
restaurant-api/src/main/java/com/restaurant/api/domain/repository/InformacionPublicaRepository.java
Other components
- API user
Connections 24
- API user → Orders API: requests
- Orders API → Order service: dispatches
- Order service → Order repository: queries
- API user → Service API: requests
- Service API → Service operation: dispatches
- Service operation → Service repository: reads and saves
- API user → Reservations API: requests
- Reservations API → Reservation service: dispatches
- Reservation service → Reservation repository: reads and saves
- API user → Payments API: requests
- Payments API → Payment service: dispatches
- Payment service → Payment repository: reads and saves
- API user → Closing API: requests
- Closing API → Closing service: dispatches
- Closing service → Closing repository: reads and saves
- API user → Incidents API: requests
- Incidents API → Incident service: dispatches
- Incident service → Incident repository: reads and saves
- API user → Availability API: requests
- Availability API → Availability service: dispatches
- Availability service → Availability repository: reads and saves
- API user → Public info API: requests
- Public info API → Public info service: dispatches
- Public info service → Public info repository: reads and saves