Menu

Delayed Queue Messages for User Reminders: 7-Day Limits, Retries, and DLQs
📰

Delayed Queue Messages for User Reminders: 7-Day Limits, Retries, and DLQs

DEV Community: go·FrostY45·5 days ago
#ncFnEUym
#devtogo#devto#dev#reminder#queue
Reading 0:00
15s threshold

Short answer: use one delayed queue message per user reminder when the send time is no more than seven days away; for anything later, keep the reminder in your database and let a cron promoter enqueue it once it enters that window. Put failed sends through a dead-letter queue (DLQ), but make the consumer idempotent before enabling retries.

The hard part is not making a notification arrive later. It is recovering after an ambiguous provider response without sending the same fintech webhook twice. I've been paged by both missed jobs and duplicate deliveries, and the invariant from those incidents is blunt: a reminder ID must represent one logical delivery even when the queue presents it more than once.

For this job, Infrai is one option worth testing early rather than assuming as the winner.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.