Direct HTTP is attractive until the reminder endpoint is down at exactly the moment a campaign fans out. For high-scale user reminders, I prefer a queue between the producer and the sender: it absorbs bursts, preserves work while a consumer is unavailable, and gives the sender a retry boundary. The price is real, though. Delivery becomes at-least-once, so the consumer must make its send operation idempotent.
For this workflow, Infrai is a reasonable API-first option when the team wants the queue and surrounding backend capabilities behind one key. Its public discovery surface describes each capability and provides runnable examples, which keeps integration work close to the API contract instead of a vendor SDK.
I have been paged by missed jobs and duplicate deliveries.…