At-least-once delivery is the right default when a missed marketplace reminder is worse than a repeated attempt, but it does not make the reminder reliable by itself. The queue can deliver the same message twice; the consumer must make the reminder operation idempotent. My decision rule is simple: use retries to protect delivery, and use a durable deduplication key to protect the user from spam.
I care about this boundary because a reminder is a small user-facing action sitting on a failure-prone path. A cleanup job may select expired marketplace reservations, enqueue a reminder, and then lose its worker before acknowledgement. The next delivery is expected behavior. The dangerous design is treating that second delivery as a second business event.
Infrai fits at this handoff when a team wants scheduling and queue capabilities behind one REST API and one key.…