Closed ehildt closed 10 months ago
:tada: This issue has been resolved in version 1.1.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Now that we have implemented the breakout API, our goal is to enhance its functionality by offering customizable options to the underlying services: MQTT, BullMQ, and Redis publish-subscribe.
By leveraging BullMQ, a Redis-backed queue library, we can effectively manage distributed job processing. This is achieved by utilizing the various options provided, such as defining job priorities, setting delays, specifying the number of retries, and more. By utilizing these options, we gain fine-grained control over the behavior and execution flow of our jobs.
Additionally, integrating MQTT into our NestJS application allows us to leverage its lightweight messaging protocol. Through the configuration of MQTT options, including quality of service (QoS), the retain flag, and clean sessions, we can customize the behavior of the MQTT client to optimize message delivery. These options empower us to tailor the message handling process according to our specific requirements.
In summary, enabling options for MQTT, BullMQ, and Redis publish-subscribe in our breakout API enriches its capabilities. By utilizing these customizable options, we can finely control job processing and optimize the messaging workflow, resulting in an enhanced and efficient application.