Azure

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
Azure 10 steps 57 seconds —views

Was this useful?

Share

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.

1 Step 1 of 10

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.

How it works

Read deeper on Azure

Twenty seconds gets the shape of an idea across. These go into how it behaves in production.

More shorts

Get new posts by email

New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.

↑↓ navigate ↵ open