🌳Idempotency is a property, not a mechanism
Idempotency describes an outcome - applying an operation N times equals applying it once. Retries, dedup keys, and upserts are mechanisms that achieve it; none of them is idempotency.
Related
Linked from
- 🌿 Distributed Systems
An evolving map of hardwon lessons about building systems that span more than one machine…
- 🌿 Retries without backoff turn a blip into an outage
A single failed request retried immediately is harmless. Ten thousand clients retrying a…
- 🌿 The outbox pattern gets you at-least-once without a shared database
The trap is the dual write: your service updates its database and publishes an event to a…
- 🌿 At-least-once delivery makes deduplication your job
Most message systems promise atleastonce delivery: your handler will see every message and…
- 🌿 Cache invalidation fails at boundaries you don't own
You can invalidate what you control. Across a boundary you don't own (a CDN, a client, a…