Blog

Tag: Idempotency

4 articles

Ten seats means ten seats, even when everyone books at once

Two people press Book for the last place. Make the capacity decision atomic, hold places with an expiry, recognize retries and tell each person what happened.

#Bookings

RnR, part 3: The XP has to add up, even when players get creative

Players will explore any points system. Give every XP award a traceable reason, define caps and windows, make corrections visible and test the awkward cases.

#Gamification

Your endpoint is idempotent. The payment still needs protection.

One order, two charges. Carry the same payment intent across retries, give uncertain results their own state and keep recovery tied to the business record.

#Idempotency

The integration works. Until someone presses the button twice.

Buttons get pressed twice and connections drop. How idempotency keeps a retried request from repeating its business effects, explained in plain English.

#APIs

Turn reading into results

Like what you’re reading? Let’s put it to work on your brand.