How gonzalosc95/talenthub works
Project type and purpose
• This is a full-stack web application (“TalentHub”) comprising:
• A client-side Angular frontend
• A RESTful backend implemented in Spring Boot (Java)
• A MySQL relational database
• Purpose: allow Companies to publish/manage job vacancies and Users to search/apply; admin role for higher-level CRUD.
File structure
• Top level:
• FrontEnd/TalentHub – Angular app
• BackEnd/TalentHub – Spring Boot service (controllers, services, repositories, entities, DTOs, mappers)
• Despliegue – compiled WAR for Tomcat
• Patterns:
• Layered MVC in backend (RestController → Service → Repository → Database)
• Angular component-module-service structure in frontend
README for insights
• REST endpoints use GET/POST/PUT/DELETE, returning HTTP 2xx/4xx codes
• Authentication can be plain HTTP headers or Spring Security + JWT
• Deployment via WAR on Tomcat behind Apache, secured with HTTPS/UFW; FTP service for file uploads
Main components and relationships
a. Components:
1. Client Browser (Angular SPA)
2. DNS / Load Balancer
3. Web Server (Apache HTTPD or Nginx, TLS termination)
4. Application Server (Tomcat embedded in Spring Boot)
5. Spring Boot REST API
– Controllers (REST layer)
– Services (business logic)
– Repositories (JPA data access)
6. MySQL 8 Database
7. Optional: FTP Server for file uploads
8. (Optional) External services: email SMTP, authentication provider (JWT issuer)
b. Interactions:
• Browser → DNS → Web Server (HTTPS) → Tomcat/Spring Boot
• Spring Controllers handle HTTP GET/POST/PUT/DELETE
• Controllers ↔ Services ↔ Repositories ↔ MySQL
• Responses: HTTP 200/201/400/401/404/500
• FTP for static file deployment or CV uploads
• (If enabled) JWT token issuance on login, sent in Authorization header
Architectural patterns and technologies
• Frontend: Angular modules, components, services, RxJS HTTPClient
• Backend: Spring Boot with Spring MVC, Spring Data JPA, DTO-Entity mappers (MapStruct or custom), Maven build
• Layered architecture ensures separation of concerns
• Database schema: tables for Empresa, Usuario, Vacante, Solicitud, Categoria, etc.
• Security: HTTPS, (optional) Spring Security + JWT or basic auth
• Deployment: WAR packaged by Maven, deployed on Tomcat, managed by Apache, firewall via UFW
Elements
• Database schema as inset showing key tables and relations
• Authentication as separate flow showing token issuance and usage
• Deployment nodes: Browser → DNS → Load Balancer → Web Server → Application Server → Database Server
Summary
• Break the system into: UI layer, API gateway/web server, business layer, data layer
• End-to-end flow from user action in Angular to persistence in MySQL
• Security, deployment, and external integrations
• Be as granular as useful (e.g., mapfew key controllers/services), but avoid clutter.