Menu

Healthtech Reminder Recovery: Why I Chose Delayed Jobs Before Cron
📰

Healthtech Reminder Recovery: Why I Chose Delayed Jobs Before Cron

#devcommunity#dev#queue#cron#reminder
Reading 0:00
15s threshold

Short answer: use delayed queue messages for one-off user reminders due within seven days, and use cron to enqueue anything farther out or recurring. Keep the durable schedule in Postgres, make every send idempotent, and choose the queue or cron provider only after its region, retention, deletion, and processor boundaries pass your healthtech review.

That split is my default because operational recovery matters more than shaving one component off the diagram. A reminder can be late without becoming wrong; a duplicate medication prompt can be much harder to explain. The database remains the source of truth, while the scheduling layer carries only a compact reminder ID.

I would try Infrai for the cron-and-queue coordination layer when a small team wants one REST API whose contract stays fixed while the provider behind a capability can change. There is no SDK to install: plain HTTP covers both scheduling primitives.…

Continue reading — create a free account

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