How ozansyk/human-resource-management-system-project works
Project type and purpose
– This is the back-end (monolithic) REST API for a full-stack Human Resource Management System (HRMS) platform (similar to Kariyer.net). It exposes endpoints to manage cities, employers, job seekers, job postings, CVs, photos, etc., stores data in PostgreSQL, and integrates with external services (cloudinary, mail check, Mernis).
File structure analysis
– src/main/java/com/ozansyk/hrms/api/controllers → REST controllers (one per resource).
– src/main/java/com/ozansyk/hrms/business/abstracts + concretes → Service interfaces and implementations (business logic).
– src/main/java/com/ozansyk/hrms/dataAccess/abstracts → Spring Data JPA repositories (DAOs).
– src/main/java/com/ozansyk/hrms/entities → JPA entities and DTOs.
– src/main/java/com/ozansyk/hrms/core/adapters → Adapter pattern for external identity (Mernis) and mail checks.
– src/main/java/com/ozansyk/hrms/core/services → Cloudinary file‐upload service.
– src/main/java/com/ozansyk/hrms/core/utilities/results → Unified Result/Response wrappers.
– src/main/resources → application.yml (dev/production profiles).
– hrms.sql → initial DB schema; Dockerfile for containerization; pom.xml + Maven wrappers.
A. External Client (React frontend)
B. API Layer (Spring MVC controllers)
C. Service Layer (business managers)
D. Data Access Layer (Spring Data Repositories)
E. Domain Model (JPA Entities + DTOs)
F. Persistence Store (PostgreSQL)
G. External Systems
– Cloudinary (photo storage)
– MailCheckService
– MernisCheckService
H. Infrastructure
– Spring Security filters (authentication/authorization)
– Docker container / application profiles
• Blue for server-side layers
• Green for external services
• Orange for database
• Gray for client
• Purple outline for Docker/container boundary