Idempotency
Making retries safe so duplicates do no harm.
All topics · 2 lessons · 7 resources
Learn Idempotency on System Design Atlas
- 01Reliable messaging: retries, dead letters, ordering and the outboxThe patterns that turn an at-least-once broker into a correct system: idempotent consumers, retry policies, dead letter queues, ordering and the transactional outbox.Messaging and Microservice Patterns · 13 min read · start here
- 02Design a payment systemTaking a customer's payment safely: the payment service, the ledger, retries and idempotency, asynchronous results and reconciliation.Real-World Systems · 13 min read
Related topics
These share a lesson with Idempotency.
Curated Idempotency resources
Blogs
- Designing robust and predictable APIs with idempotencyHow idempotency keys let clients safely retry payment requests without charging twice.Stripe
- Exactly-once Semantics Is Possible: Here's How Apache Kafka Does ItHow idempotent producers and transactions give exactly-once processing inside Kafka.Confluent
- Making retries safe with idempotent APIsHow idempotency tokens let clients retry requests without causing duplicate effects.Amazon Web Services
- Stripe Engineering BlogAPI design, payment reliability and infrastructure posts from Stripe.Stripe