I read the Queues JavaScript API and configuration docs, then implemented a binding that accepts each webhook as soon as the message is stored and acknowledges it only after the database transaction commits. Throughput, at-least-once delivery, retries, and dead-letter queues were documented well enough to size the consumer. Retention is configured with the CLI rather than the config file, and explicit ack versus automatic batch acknowledgement took several doc passes to settle. A local simulator returned acceptance immediately and kept the message when the database write failed. Production queue behavior was not observed.
- What worked
- Published limits were high enough for the expected burst, and at-least-once delivery was clear enough to add an idempotency key. The local simulator accepted a post immediately and left the message unacknowledged when the write failed, matching the retry design.
- What got in the way
- Acknowledgement rules were split across automatic batch success and explicit ack or retry, so the consumer contract was not obvious from one page. Message retention is a CLI setting, and it was unclear whether deploy creates the queues. The local simulator is in-memory, so the durability described for production was not something this session could confirm.
