The outage lasted 18 minutes. Your retries lasted 4 seconds.
720 good orders in the dead-letter queue, and not one of them was poison.
What you'll learn
- Why ten redeliveries take about four seconds, not four minutes
- That MaxDeliveryCount caps attempts and says nothing at all about time
- How to build the backoff Service Bus does not give you, with ScheduledEnqueueTimeUtc
Share this passage
Drawing…
Understand it one step at a time
The short runs these in order in about 50 seconds. Here they are written out — pick any step to jump the short straight to it.
40 orders a minute, all fine
A Service Bus queue, one worker, and a downstream inventory API. Every setting on this queue is still the untouched Azure default.
Frequently asked questions
- Does MaxDeliveryCount give you a retry window?
- No — it caps the number of delivery attempts, not the time between them. With no backoff, ten attempts can burn through in about four seconds, not the four minutes you might assume, dead-lettering everything if a dependency is down for even a short outage.
- How do you add backoff to Service Bus retries?
- Service Bus doesn't provide one natively — you build it yourself, typically by re-scheduling a redelivery with ScheduledEnqueueTimeUtc set some interval in the future instead of letting it retry immediately.
Free app · no app store
These are built for a phone
Every short is drawn at full portrait height, the shape a phone already is. Installed, it opens full-bleed with no address bar across the top — and the whole library reads offline.
Read deeper on Azure
Twenty seconds gets the shape of an idea across. These go into how it behaves in production.
-
AI Bot Attacks on a Mobile App Login, and How Azure Stops Them
A script tries 8,000 passwords a minute against your login API at 3am. Rate limiting, smart lockout and Defender for Cloud make speed the losing move.
-
Azure Key Vault Explained: The One Secret Tutorials Never Remove
Moving every secret into Key Vault leaves exactly one behind: the credential that opens the vault. A managed identity is what removes it.
-
How to Secure a Mobile API on Azure in Five Steps, in the Right Order
HTTPS only, authentication, authorization, secrets and monitoring: five steps to secure a mobile API on Azure, and why the order carries most of the value.
More shorts
-
Azure
Money debited. Order failed.
10 steps · 56s
-
Azure
One tap. Two orders.
10 steps · 57s
-
Azure
1.6 million downloads. One photo.
10 steps · 58s
Get new posts by email
New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.
MSDEVBUILD
/ blog Multi-Stack Dev Build · by Suthahar Azure