4 ms·
If you only need to schedule for a handful of different delays, you can do so with RabbitMQ by having a queue with no consumers and a certain timeout with a “de
by Nextgrid 7y ago
If you only need to schedule for a handful of different delays, you can do so with RabbitMQ by having a queue with no consumers and a certain timeout with a “dead letter queue” configured. Messages will stay in there until they reach the timeout and will then be delivered in the dead letter queue. I’ve seen this approach being used successfully before.
- jjeaff 7y agoYes, but I think a common use case would be scheduling reminders, notifications, and emails for users. Which runs into the millions of scheduled tasks at different intervals pretty quickly.
- Nextgrid 7y agoFor a handful of fixed intervals however (like notifications), the RabbitMQ solution works well - have one queue for "In an hour", another one for "in a day" and so on. For completely arbitrary intervals you could look at Celery and its "Celery Beat" scheduler, otherwise for a proprietary solution look into Google Cloud Tasks which seems to have a "scheduled_time" parameter (haven't tried it personally though): https://cloud.google.com/tasks/docs/reference/rpc/google.cloud.tasks.v2#google.cloud.tasks.v2.Task https://cloud.google.com/tasks/docs/reference/rpc/google.clo...