novu icon indicating copy to clipboard operation
novu copied to clipboard

Queuing of notifications

Open ChakshuGautam opened this issue 2 years ago • 3 comments

What and Why?

We have a bunch of notification providers that don't provide good uptime and have to tried again and again. Need a mechanism for failure management and re-trigger notifications after a backoff. Currently I wasn't able to find a queue being persisted for the following use cases

  • Bulk notifications
  • Scheduled notifications
  • Retrying on failure

If there is something already there, if you can point me to the relevant code sections, that would be great. Thanks.

ChakshuGautam avatar Jan 18 '22 01:01 ChakshuGautam

Hi @ChakshuGautam how about bull queue package ? it uses redis for queuing messages and can cover the scheduled notifications and retrying on failure.

for more info : https://www.npmjs.com/package/bull

kharbanda14 avatar Jan 27 '22 16:01 kharbanda14

We should create queue based on external solutions like rabbitMQ and Kafka, etc

DomnicAmalan avatar Apr 08 '22 18:04 DomnicAmalan

Is this issue still relevant @scopsy?

jainpawan21 avatar Aug 11 '22 16:08 jainpawan21

We are using internally Bullmq overe redis with the provided functionality that was released on 0.7.0 (if i recall correctly :P)

So we can close this for now.

scopsy avatar Nov 27 '22 13:11 scopsy