How jcomyn/proyecto-gpi works
Project type and purpose
• This is a full-stack car-rental system (“sistema de alquiler de coches”) built with:
• A Java/Spring Boot backend following a hexagonal (ports-and-adapters) architecture
• A React frontend (Material Dashboard template)
• A file-based H2 database
• Docker and docker-compose for local deployment
File structure
• Top-level:
• backend/ – Spring Boot code, organized in “application”, “domain”, “infrastructure” packages
• front/ – React app scaffolded around MUI-based Material Dashboard
• docker-compose.yml, init.sql – orchestration and DB init
• backend layers:
• application/ – DTOs, exceptions, service interfaces and their use-case logic
• domain/ – entities and repository interfaces (ports)
• infrastructure/ – REST controllers (adapters/entry points), persistence adapters (JPA + custom impl), mappers, exception handlers, CORS config
• front layers:
• src/services – API clients calling backend HTTP endpoints
• src/hooks, src/context – state management
• src/components, src/layouts, src/paginas – UI components and page flows
README
• The README confirms a Docker-Compose workflow and describes the system’s purpose: car-rental management.
Elements
• User → Frontend → Backend REST → DB
• Frontend (blue), Backend ports/adapters (orange), Domain (green), DB (gray)
Detail is key
• Don’t omit layers: explicitly show DTOs, mappers, exception handlers
• Hexagonal structure: encapsulate domain inside application layer, surrounded by adapters
• External boundary (browser, Docker network)