3 ms·
The queue/DLQ in this case is on Stripe's end. Once the WAF problem was fixed, Stripe ran the webhooks correctly.
by wlonkly 4y ago
The queue/DLQ in this case is on Stripe's end. Once the WAF problem was fixed, Stripe ran the webhooks correctly.
- amluto 4y agoWith a real queue, dropping one message on the underlying transport will either be detected quickly and obviously on both ends, or will be recovered automatically, or both. The implementation could be as simple as a queue id and sequence number in the POST along with a way to request replay (via GET to Stripe) of old messages indexed by the same id and sequence number and a way to periodically ask for the latest sequence number.