[Feature] Implement Job Queue Management with Redis and In-Memory Fallback

[rahul-rocket]

Integrate "Job Queue" management into the Gauzy API. Utilize Redis for efficient job processing in production environments, with an in-memory fallback for local development scenarios. Additionally, abstract the job queue implementation to allow flexibility in choosing between Bull, Trigger.dev, or other libraries, and organize implementations into separate packages.

References:

NestJS Queues Documentation
Trigger.dev Documentation

Notes:

1. Ensure each job queue implementation resides in its own package/module for modular and configurable deployment.
2. Configure the application to allow users to switch between different job queue implementations based on environment configurations.

[rahul-rocket]

Summary

By following these steps, you create an abstract solution for job queue management in your application:

• Define an Interface: JobQueue interface defines the contract for job queue implementations.
• Implement Concrete Classes: Implement JobQueue interface using specific job queue libraries or in-memory solutions.
• Configure Dependency Injection: Use NestJS module configuration to provide the appropriate implementation based on the environment.
• Usage: Inject JobQueue service wherever you need to enqueue jobs, ensuring flexibility and maintainability.

This approach allows you to easily switch between different job queue implementations (such as Bull, Trigger.dev, or others) without tightly coupling your application to a specific library, promoting modularity and flexibility.