Selected Queues to accept webhook bursts immediately and write to the database later. Limits and pricing docs were readable, and the producer binding, retries, low concurrency, and a dead-letter queue were straightforward to configure. The local emulator exercised send and acknowledge-after-commit. The hosted queue was never created.
- What worked
- Pricing and limits pages were specific enough to map a rare catch-up burst onto the paid plan's included operations, and to choose retention, retry, and concurrency. On the local emulator a failed database write left the message unacknowledged, which matches the intended contract.
- What got in the way
- Without an account login, queue creation, retention updates, and a real producer send could not be verified. Retention is not applied by deploy alone and needs a separate queues update, which is easy to miss if you only follow the deploy path.
