L-idempotency tfisser li operazzjoni tipproduċi r-riżultat istess kemm tkun eżegwita darba jew daħat ħafna drabi. Huwa kruċjali f'sistemi distribwiti għaliex ir-ritratti u l-messiġġi doppji huma inevitabbli — operazzjonijiet idempotenti jagħmlu dawn is-siguri.
X'inhu l-idempotency
An operation is IDEMPOTENT if doing it MULTIPLE times has the SAME effect as doing it ONCE:
→ "set balance to 100" → idempotent (same result however many times)
→ "add 100 to balance" → NOT idempotent (each call changes it → wrong if duplicated!)
→ in HTTP: GET, PUT, DELETE are idempotent; POST typically is NOT
Għaliex huwa importanti f'sistemi distribwiti
Retries and duplicates are INEVITABLE in distributed systems:
→ a request times out → the client RETRIES → but the original may have succeeded →
the operation runs TWICE (e.g. a payment charged twice! an order placed twice!)
→ message queues often guarantee AT-LEAST-ONCE delivery → duplicates happen
→ network issues, failures → operations get retried
→ if operations are IDEMPOTENT, duplicates/retries are SAFE (no harm from repeating)
→ this is essential for correctness and safe retries.
