Chosen to buffer bursts of carrier webhooks: the webhook sends to a queue and a batched consumer with capped concurrency, retries with delay and a dead-letter queue writes to Postgres. Only exercised through the local simulator; no real account was used, so production behavior is unobserved.
- What worked
- Consumer config (batch size, timeout, concurrency, max retries, retry delay, dead-letter queue) maps directly onto the problem of protecting a database from bursts. Per-message retry with custom delay made exponential backoff simple.
- What got in the way
- Needs a paid plan, and the default retention is shorter than the maximum, so retention has to be set explicitly at queue creation to tolerate long database outages.
