How jhonnatanhhm/envifo-java-backend-api-rest works
Project type and purpose
• This is a single-service Java Spring Boot REST API backend.
• Purpose: expose HTTP endpoints to manage customers, projects, materials, textures, 3D designs, etc.; enforce security via JWT; persist data in PostgreSQL; handle migrations with Flyway; process asynchronous messages via RabbitMQ; and send recovery emails.
File structure
• layers/hexagonal approach under src/main/java/com/envifo_backend_java/Envifo_backend_java:
• interfaces/controller – REST controllers (API layer)
• application/dto & application/service – DTOs and orchestration services (use-case layer)
• domain/model & domain/service & domain/repository – entities, business interfaces, repository interfaces (domain layer)
• infrastructure/config – Spring configs (DB, Flyway, RabbitMQ, security, Swagger)
• infrastructure/persistence/repository – JPA repository implementations (data access)
• infrastructure/messaging – RabbitMQ listeners (event handling)
• infrastructure/security – JWT filters, token factory, entry point (security infra)
• infrastructure/exceptions – global exception handling
• Dockerfile, pom.xml, Maven wrapper, .mvn indicate containerized, Maven-driven build and deployment.
• src/main/resources/db/migration holds Flyway scripts.
• src/main/resources/templates holds email template.
README
• Confirms tech stack: Spring Boot, Spring Security, JWT, JPA, PostgreSQL.
• Mentions API REST, token generation/validation, DB management.