Webhook delivery: at least once, to systems you don't control
Delivering a million webhooks an hour to receivers that are slow, down or lying: why at-least-once plus idempotent receivers is the only honest guarantee, the event bus, dispatcher, partitioned queues and workers, a 39-hour retry schedule, HMAC signatures and replay protection, sizing the workers, and getting a receiver that was down for 2 hours back in 13 minutes instead of 2 hours.
01 · Previously
W02 · DAY 04 · Webhook Delivery System
From request and response to events.
Previously: the payment stack
Previously, on Day 3, you finished the payment pipeline: timeouts so you never wait forever, idempotency so retries are safe, and circuit breakers so you fail fast when something's broken.
0:00 / 16:59