Short answer: at-least-once delivery makes a reminder safer to retry, but unsafe to execute blindly. A standard queue may deliver the same renewal-reminder job more than once, so its impact on reliability is determined by the notification effect: make it idempotent, record enough state to recover after a deadline, and retain only the evidence needed to explain a decision to a user.
For an e-commerce system, the concrete job is easy to state: send a reminder after a merchant-defined business deadline, such as 09:00 on the next working day. The difficult part is deciding what happens after a timeout, a worker restart, or a successful send followed by a lost acknowledgement. The queue's promise is delivery of work, not exactly-once execution of the side effect.
How does at-least-once delivery in standard queues affect reliability?
It changes the default failure decision. If the worker cannot prove that processing finished, the recovery-friendly action is to make the job visible again and try it.…