Node.js Reminder Queue Practices: Creating Background Jobs with Delivery Guarantees
TL;DR: The best practices for creating a Node.js background job queue for reminders are to make work safe to repeat, record every state transition, stop admitting new jobs before shutdown, and let leases expire only after the handler releases its claim. A duplicate delivery is usually recoverable; a reminder marked complete before the external notification succeeds is not. A rate-limited worker…
We haven't written up this one. Dev.to has the full story — the link below goes straight to it.