How jonathnawill/desafio-pacto-vaga-back works
Project Type and Purpose
• This is a monolithic Spring Boot back-end application that serves as the API layer for an internal recruitment system.
• It exposes REST endpoints for user authentication (JWT), job vacancy management, candidate applications, skills management, and user management.
• Although there is a front-end (Angular) referenced in the README, the provided file tree only contains the back-end.
File Structure and Architectural Layers
• Top-level artifacts:
• pom.xml – Maven build and dependency management
• mvnw/mvnw.cmd – Maven wrapper scripts
• src/main/java/com/desafio/pacto – application code
• src/main/resources – environment-specific and default properties
• src/test – unit/integration tests
• Layered organization under src/main/java:
• config – Spring Security, CORS, filters, entry points
• controller – REST controllers mapping HTTP requests to service calls
• services & services/impl – business logic interfaces and implementations
• repositories – Spring Data JPA interfaces for DB access
• entities (+dto, enums, converters, listeners) – domain models and data-transfer objects
• util/parser – mapping between entities and DTOs
• Key cross-cutting concerns:
• Security (JWT token filter, entry point, WebConfig for CORS)
• Exception handling through Spring mechanisms (not shown but implied)
• Environment profiles (application-dev.properties, application-prod.properties)
Insights from README
• Functionality includes: JWT authentication, role-based authorization (Admin, User), CRUD on vacancies, user candidacies, candidate dashboard, evaluation features.
• Front-end is an Angular application served separately (http://localhost:4200) that consumes this API at /api/** endpoints.
• Database is external (production on Railway) but modeled with Spring Data JPA.