|
|
|
|
|
by modal-soul
2216 days ago
|
|
I've been using something like this for exponential backoffs, but I think it'd work for this case as well. Let's say you've got one exchange and one main queue for processing: jobs.exchange and jobs.queue respectively. If you need to schedule something for later, you'd assert a new queue with a TTL for the target amount of time (scheduled-jobs-<time>.queue). Also set an expiry of some amount of time, so it'd get cleaned up if nothing had been scheduled for that particular time in a while. Finally, have its dead-letter-exchange set to jobs.exchange. This could lead to a bunch of temporary queues, but the expiration should clean them up when they haven't been used for a bit. |
|