How gastrobaralemans/backend works
Project type and purpose
• This is a Spring Boot monolithic backend service (Java) for the “Gastrobar Alemans”/“Unibytes” project.
• It exposes RESTful endpoints for authentication, menu management, order processing, reservations, comments/posts, and notifications.
File structure
• Top-level: pom.xml (Maven), mvnw, .mvn for build tool; src/main/java for application code; src/main/resources for config; src/test for unit/integration tests.
• Package breakdown under com.gastrobar_alemans_backend:
• DTO – data transfer objects between layers
• model – JPA entities and request models
• repository – Spring Data JPA interfaces for persistence
• service – business logic
• controllers – REST API layer
• config – Web, Security, Encoder configurations
• security – JWT utilities and filters
• advice – global exception handlers
• application.properties holds database and JWT settings.
README
• Very brief: “Repositorio para el backend del proyecto Unibytes.”
Detailed breakdown (to capture essential elements)
• Package/controller group: AuthController, RegisterController
• Package/controller group: MenuController + PlatilloIngredienteController + IngredienteController
• Package/controller group: PedidoController + ReserveController
• Repository cluster: all *Repository interfaces
• Service cluster: MenuService, PedidoService, PersonDetailsService
• Security cluster: JwtAuthenticationFilter, JWTUtil, SecurityConfig
• Model/DTO cluster: Entities vs. DTOs for request/response mapping