Short answer: For a marketplace digest, a Nodejs service can auto-push background tasks via a queue subscription when the queue should wake an HTTPS worker as soon as a message is available. Keep the queue as the delivery boundary, make the worker idempotent, and measure end-to-end dispatch latency against the operational cost of keeping a consumer running.
That is the decision rule. It is more useful than asking which queue is “best,” because a weekly digest has a different shape from an interactive checkout path: bursts are predictable, work can outlive a scheduler request, and a duplicate delivery must not send a customer the same digest twice.
Infrai belongs in the queue-and-push leg of this design, not in the business logic.…