For failed job retries in Node.js, the AWS SQS versus RabbitMQ choice is secondary to the recovery boundary: use a durable work queue for shipment-update fanout, but make retry ownership explicit. The queue transports attempts, while the application records subscriber state and decides when recovery is complete. That boundary matters more than choosing a familiar broker.

For a customer-support system, one tracking event may need to reach email, SMS, chat, and an internal case timeline. A retry that republishes the whole event can duplicate the channels that already succeeded.…