Used as the durable buffer between webhook acceptance and database writes, with a producer send in the request path and a batched consumer for database inserts plus retries and a dead-letter queue. Local development used an in-memory fallback.
- What worked
- Configuration model was clear: producer binding, consumer batch size, retry count, and dead-letter routing mapped directly onto the burst, timeout, and no-loss requirements.
- What got in the way
- No live queue was exercised in the record; durability, retry, and dead-letter behavior were reasoned from docs and config rather than observed against the real service.
