Integrate Context and Dependency Injection (CDI) into Job Queue System

[jgambarios]

Parent Issue

#29474

User Story

Enhance the design and implementation of our job handling system by incorporating Context and Dependency Injection (CDI) using Weld. This improvement aims to increase modularity, flexibility, and testability of the job queue system.

Objectives:

1. Implement CDI throughout the job queue system to manage dependencies and lifecycle of components.
2. Utilize CDI features to make the system more configurable and easier to extend.
3. Improve testability by leveraging CDI for easier mocking and dependency substitution.

Tasks:

1. Refactor key components to be CDI-managed beans:
   • JobQueueManagerAPI implementation
   • JobQueue implementations (PostgresJobQueue, potential future implementations)
   • JobProcessor implementations
   • CircuitBreaker
   • RetryStrategy implementations
2. Implement CDI producers for configurable components (e.g., JobQueue implementation selection).
3. Utilize CDI qualifiers for different implementations of the same interface (e.g., @postgres, @redis for JobQueue).
4. Implement CDI events for job state changes to decouple components.
5. Use @PostConstruct and @PreDestroy for proper initialization and cleanup of components.
6. Update unit tests to work with CDI, utilizing test-specific alternatives where necessary.
7. Document the new CDI-based architecture and update any relevant diagrams.

Benefits:

• Improved modularity and separation of concerns
• Easier management of dependencies and component lifecycles
• More flexible configuration options
• Enhanced testability through easier mocking and dependency substitution
• Preparation for future extensibility (e.g., adding new job queue implementations)

Acceptance Criteria

1. All key components of the job queue system are managed by CDI.
2. The system can be configured to use different implementations (e.g., job queues) through CDI mechanisms.
3. Unit and integration tests are updated to work with the CDI-based architecture.
4. Documentation is updated to reflect the new CDI-based design.

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average