Short answer: For failed job retries in Node.js, AWS SQS is the simpler default than RabbitMQ when a managed DLQ and retry policy fit your trust boundary; RabbitMQ wins when you need broker control. For a healthtech cleanup, keep the cron request short and let an idempotent worker process the job.
Healthtech cleanup jobs should be scheduled briefly and processed durably. My default is a cron trigger that enqueues a bounded cleanup request, followed by an idempotent worker with a dead-letter path. That keeps a web request out of the work and makes failed delivery visible.
The evaluation constraint is data handling: where does protected data live, who processes it, how long is it retained, and what happens when delivery fails? AWS SQS is usually the lower-maintenance choice when its retry policy and dead-letter queues match the job. RabbitMQ is the better fit when you need broker-level control, routing, or a deployment boundary you already operate.…