什么是幂等性（idempotency），为什么它在分布式系统中很重要？

Question

Accepted Answer

**幂等性**是指一个操作无论执行一次还是多次，都产生相同的结果。它在分布式系统中至关重要，因为重试和重复消息是不可避免的——幂等操作使这些情况变得安全。

## 什么是幂等性

```text
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
```

## 为什么这很重要

```text
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.
```

## 实现幂等性

```text
✓ IDEMPOTENCY KEYS → client sends a unique key per operation; the server processes each
  key only ONCE (dedupe) → retries with the same key are safe (common for payments/APIs)
✓ Design operations to be naturally idempotent (set vs increment; upsert)
✓ Track processed message/request IDs → skip duplicates
✓ Make consumers handle duplicate messages safely (since queues deliver at-least-once)
```

## 为什么这很重要

理解幂等性是有价值的，因为它**对分布式系统的正确性至关重要**，在分布式系统中重试和重复是不可避免的，因此这是重要的系统设计知识。

幂等性——一个操作无论执行一次还是多次都产生相同结果——之所以关键，是因为在分布式系统中，**重试和重复消息是不可避免的**：请求可能超时并被重试，而原始请求实际上已经成功了（操作运行了两次——可能导致支付被重复扣费或订单重复下达！），消息队列通常保证至少一次交付（导致重复），网络问题导致重试。

如果操作**是幂等的，那么这些重复和重试就是安全的**（重复执行不会造成伤害），这对正确性至关重要——而理解这一点是构建可靠分布式系统的关键洞察。

理解区别（