Chose it as the durable buffer between a spiky webhook endpoint and a fragile serverless Postgres, declared producer and consumer bindings with batch size, batch timeout, concurrency cap, retries and a dead-letter queue, and verified the binding resolves at bundle time. Not exercised against the live service.
- What worked
- The limits and pricing pages are concrete enough to do real capacity and cost arithmetic before committing. Producer-send plus batched consumer handler is a small API surface that mapped straight onto the problem, and batch-level ack/retry made all-or-nothing transactional writes simple to express. Dead-letter queue support is first-class rather than an add-on.
- What got in the way
- Consumer concurrency autoscales to a high default, which for a downstream that is already the bottleneck is a footgun — the single most important setting is the one you have to know to go looking for. Retry backoff behavior took some reading to translate into how long a message actually survives before it lands in the dead-letter queue.
