How navneetprabhakar/executor works
Project type and purpose
• This is a Spring Boot microservice (backend application) exposing REST APIs for uploading files and processing them asynchronously via a thread pool (ExecutorService/ThreadPoolTaskExecutor).
• The primary use case: clients upload files, the service enqueues processing tasks, persists metadata in a database, and provides status updates.
File structure
• Top-level build files: build.gradle, settings.gradle, .gitignore.
• src/main/java/com/navneet/executor:
• configs – ThreadPoolTaskExecutor bean configuration
• constants – StatusEnum (task states)
• controller – TaskController (REST endpoints)
• data/models – JPA entities (Customer, Tasks)
• data/repo – Spring Data JPA repositories
• models – API DTOs (ServiceRequest/Response, UploadRequest/Response, TaskStatus)
• service – UploadService interface, helper and implementation
• threads – ProcessFileUploadTask (Runnable job)
• utils – FileUtils (file operations)
• src/main/resources/application.properties – thread-pool and datasource settings.
README for additional insights
• Confirms focus on JDK ExecutorService and Spring ThreadPoolTaskExecutor.
• REST APIs to upload and process.
a. Main components
1. Client (e.g., Web UI or CURL)
2. TaskController (Spring MVC layer)
3. UploadService (business logic)
4. ThreadPoolTaskExecutor (configured thread pool)
5. ProcessFileUploadTask (worker threads)
6. File Storage (local FS or external blob store)
7. Database (Tasks, Customer tables via Spring Data JPA)
8. Utilities (FileUtils)
9. Configuration (ThreadPoolExecutorConfig)
b. Relationships & interactions
• Client → TaskController: sends UploadRequest
• TaskController → UploadService: invokes uploadFile()
• UploadService:
• persists initial task record via TasksRepo
• submits ProcessFileUploadTask to ThreadPoolTaskExecutor
• ThreadPoolTaskExecutor → ProcessFileUploadTask: picks up tasks asynchronously
• ProcessFileUploadTask:
• uses FileUtils to store/process files
• updates task status in DB via TasksRepo
• Client can poll TaskController for TaskStatus (reads from DB).
c. Architectural patterns & design principles
• Layered MVC: Controller → Service → Repository
• Asynchronous processing: Producer (controller/service) & Consumer (thread pool workers)
• Dependency injection for configs, services, repos
• Separation of concerns: DTOs vs. Entities vs. Helpers
d. Key technologies & frameworks
• Spring Boot (auto-configuration, embedded server)
• Spring MVC (REST controllers)
• Spring Data JPA (repository layer)
• ThreadPoolTaskExecutor (configurable thread pool)
• JDK ExecutorService under the hood
• Java 8+ features (Runnable, enums)