The system design library
Search and filter every curated system design video, article, repository and paper in one place.
7 resources
10 Tips for Building Resilient Payment Systems
Practical rules from Shopify's payments team: idempotency, retries, reconciliation and more.
Case StudiesIntermediateRead hereBy Shopify Engineering · Shopify
Designing robust and predictable APIs with idempotency
How idempotency keys let clients safely retry payment requests without charging twice.
BlogsIntermediateBy Brandur Leach · Stripe
End-to-End Arguments in System Design (paper)
The principle that reliability is best checked at the endpoints, behind many design choices in networking and retries.
PapersIntermediateBy Saltzer, Reed and Clark · MIT
Exactly-once Semantics Is Possible: Here's How Apache Kafka Does It
How idempotent producers and transactions give exactly-once processing inside Kafka.
BlogsAdvancedBy Neha Narkhede · Confluent
Making retries safe with idempotent APIs
How idempotency tokens let clients retry requests without causing duplicate effects.
BlogsIntermediateBy Amazon Builders' Library · Amazon Web Services
Pattern: Transactional outbox
Publishing events reliably by saving them in the same database transaction as the change.
DocumentationIntermediateBy Chris Richardson · microservices.io
Stripe Engineering Blog
API design, payment reliability and infrastructure posts from Stripe.
BlogsIntermediateBy Stripe engineers · Stripe