Used the queue binding as the durable buffer for carrier webhooks: authenticate and validate on the request, send the payload, return success immediately, then drain with a consumer that retries and dead-letters after five failures. Official pricing, getting-started, and limits pages were fetched because plan and throughput rules were unclear. Code and a config dry-run landed; a live queue was never created or exercised.
- What worked
- Producer send plus a consumer with ack, per-message retry, a dead-letter queue, and low concurrency mapped cleanly onto the Workers handler model and kept the database off the request path.
- What got in the way
- Public docs disagreed on whether queues need a paid Workers plan or work on free, including daily operation caps versus a burst of thousands of messages. Live account, plan, queue creation, and secrets were still required after the code change, so runtime queue behavior was not observed.
