Idempotency ni nini, na idempotency keys hufanyaje retries kuwa salama?

Question

IT Interview Practice · Accepted Answer

**Idempotency** humaanisha kufanya operesheni **mara nyingi kuna athari sawa na kuifanya mara moja**. Ni muhimu kwa sababu mitandao haiaminiki: wakati client hutuma request na response haiwahi kufika, haiwezi kujua kama server iliichakata. Ikirudia, operesheni isiyo idempotent inaweza kukimbia mara mbili.

## Tatizo

```text
Client ──POST /payments {$100}──▶ Server   (charges $100 ✓)
Client ◀────────X (timeout)────── Server   (response lost)
Client ──POST /payments {$100}──▶ Server   (charges $100 AGAIN ✗ → $200!)
```

`GET`, `PUT`, na `DELETE` ni idempotent kiasili, hivyo kuzirudia ni salama. `POST` **si** — hapa ndipo hasa malipo yanayojirudia na orders zinazojirudia hutokea.

## Suluhisho: idempotency keys

Client huzalisha **key ya kipekee** (kwa kawaida UUID) kwa operesheni ya kimantiki na huituma katika header. Server huhifadhi key pamoja na matokeo; ikiwa key ile ile itafika tena, hurudisha matokeo **yaliyohifadhiwa** badala ya kutekeleza tena.

```http
POST /payments HTTP/1.1
Idempotency-Key: 5f2b8c1e-3a4d-4e6f-9c0b-1a2b3c4d5e6f
Content-Type: application/json

{ "amount": 100, "currency": "usd" }
```

```text
Server logic on receiving a request with an Idempotency-Key:
  1. Look up the key in a store (e.g. Redis/DB).
  2. If found → return the saved response (no re-charge).      ← the retry case
  3. If not  → process, save (key → response), then return.
  (Wrap 3 in a transaction / lock so concurrent retries don't double-execute.)
```

**Key ile ile** wakati wa retry hutoa `200` ile ile na payment ile ile — mteja hutozwa mara moja. Hivi ndivyo hasa API ya Stripe inavyofanya kazi.

## Kwa nini ni muhimu

Swali hili hutenganisha wahandisi wanaobuni kwa happy path na wale wanaobuni kwa **kushindwa (failure)**, jambo ambalo ndilo msingi wa uaminifu wa production. Mifumo ya distributed huhakikisha kwamba timeouts na kushindwa kwa sehemu *kutatokea*, hivyo endpoint yoyote yenye side effects — payments, orders, kutuma pesa — inahitaji mkakati wa retry, na "rudia tu" ni hatari kwa `POST`. Mhoji anataka kusikia utambuzi wa sehemu mbili: kwanza, kwamba idempotency ni sifa unayoweza *kuibuni ndani* (kufanya `PUT`/`DELETE` salama kiasili, na kumpa `POST` **idempotency key** wakati haiwezi kuwa hivyo), na pili, undani tata wa concurrency — retries mbili zinazofika kwa wakati mmoja hazipaswi zote kutekeleza, hivyo ukaguzi wa key na uandishi zinahitaji lock au unique constraint. Kupata hili sahihi ni tofauti kati ya kumtoza mteja mara moja na kumtoza mara mbili, ndiyo sababu kila API ya payments na biashara ya kweli huitekeleza.

Tatizo

Suluhisho: idempotency keys

Kwa nini ni muhimu

Maswali yanayohusiana