How bohdanmoldavets/task-management-system works
Project type and purpose
• This is a backend‐focused, RESTful Task Management System built with Spring Boot. It exposes a set of APIs to manage tasks and employees, secures endpoints using JWT/Spring Security, sends email notifications, and persists data in PostgreSQL with Flyway migrations. There is no “browser” frontend shipped here—clients interact over HTTP (e.g., via Swagger UI or any HTTP client).
File structure
• Top level:
• Dockerfile / docker-compose.yaml – containerization setup
• pom.xml – Maven build and dependency management
• src/main/java/com/moldavets/task_management_system – application code
• src/main/resources/db/migration – Flyway migrations
• src/main/resources/application.properties – configuration
• auth – JWT configuration, filters, controllers, DTOs, services, repositories
• employee – CRUD controllers, DTOs, mappers, service, repository
• task – similar to employee but for task entities
• email – email‐sending service
• exception – global exception handler and models
• utils – shared base entity, enums, token utilities
• Tests mirror the structure under src/test/java.
README for additional insights
• Describes the stack (Java 21, Spring Boot, Security, JPA/Hibernate, PostgreSQL, Flyway, Swagger, Docker)
• Lists key features: authentication, role-based access, email notification, migration scripts, REST docs
Essential architectural elements
• Don’t just list packages—show how data flows through JWT authentication, gets mapped by controllers, handled by services, persisted by repositories, and triggers email notifications.
• Docker layer to show containerization and how the app connects to PostgreSQL.
• Flyway in the startup path from application → Flyway → DB schema.
• Use legends or annotations for frameworks/technologies (e.g., “Spring Data JPA → PostgreSQL”, “Swagger UI at /swagger-ui”).