How abhijeetkadtan/railsebackendassignment works
Project type and purpose
• This is a single-service Spring Boot backend application (a monolith) that provides a REST API for workforce management (task creation, update, assignment, fetch).
• The README confirms it’s purely a backend take-home assignment using Java 17, Gradle, and exposes endpoints under /task-mgmt.
File structure
• Top level:
• build & CI: build.gradle, gradlew(.bat), Gradle wrapper under gradle/wrapper
• source code: src/main/java/com/railse/hiring/workforcemgmt/...
• resource config: src/main/resources/application.properties
• tests: src/test/java/com/railse/hiring/workforcemgmt/...
• Within workforcemgmt:
• controller layer (controller/…Controller.java)
• service layer (service interfaces + service/impl)
• repository layer (repository with InMemoryTaskRepository)
• domain model (model + enums)
• DTOs (dto) and mappers (mapper)
• common concerns (exceptions, response wrappers)
README for additional insights
• Endpoints: GET /task-mgmt/{id}, POST /create, /update, /assign-by-ref, /fetch-by-date/v2
• No external systems (e.g., message brokers or other microservices) are listed