- Published on
How to prevent race conditions in backend systems by naming the invariant, enforcing it at durable boundaries, and testing overlapping requests and retries.
Distributed-systems
All Posts
- software-engineering (26)
- backend (24)
- reliability (21)
- distributed-systems (15)
- databases (14)
- production-systems (9)
- performance (8)
- architecture (7)
- api-design (6)
- testing (5)
- microservices (5)
- fundamentals (4)
- observability (4)
- debugging (4)
- sql (4)
- best-practices (3)
- cascading-failures (3)
- systems (3)
- code-review (2)
- engineering-process (2)
- ci (2)
- Published on
How to implement the transactional outbox pattern for reliable event publishing: schema design, relay claiming, retries, duplicates, ordering, and CDC.- Published on
How to run background jobs safely in production with replay-safe handlers, bounded retries, dead-letter triage, visibility timeouts, and queue dashboards.- Published on
How to design API idempotency keys for retries, duplicate POST requests, payload mismatch, TTL, in-progress requests, and safe response replay.- Published on
How rate limiting, backpressure, and load shedding keep microservices inside safe capacity, with failure timelines, admission controls, and rollout steps.