One tap. Two orders.
A double tap charges the customer twice.
What you'll learn
- Why a double tap or a retry after a timeout creates two orders
- What an idempotency key is, and why the app has to create it
- How a unique index in Azure SQL stops the duplicate, on any server
Share this passage
Drawing…
Understand it one step at a time
The short runs these in order in about 57 seconds. Here they are written out — pick any step to jump the short straight to it.
One tap, two orders
A double tap sends the same order twice, to two different servers.
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
1.6 million downloads. One photo.
10 steps · 58s
-
Azure
Your public API has no login — and no identity
8 steps · 26s
Get new posts by email
New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.