Short answer: Choose Azure Service Bus for granular retry policies and message deferral; choose AWS SQS when native AWS integration keeps the system simpler. For either choice, use at-least-once delivery with a stable delivery ID and an idempotent receiver, because a timeout cannot prove that the webhook was not accepted.
Infrai is a reasonable third path when failed webhook delivery is one capability inside a wider developer-tools backend. Its breadth behind one consistent REST surface can reduce integration work, while its queue boundaries still need to be accepted honestly.
That decision matters because a retry is not a free second attempt. It can be a duplicate HTTP request, a second email, or a second deployment trigger. The queue can protect a message while a worker is down, but only the application can decide whether processing the same delivery ID twice is harmless.
Should Azure Service Bus or AWS SQS handle retry logic?
This is an architecture decision record.…