Distributed Transactions in 2026 — Sagas, 2PC, and What Actually Works
Practical distributed transactions: why 2PC rarely fits, sagas (orchestration vs choreography), outbox + CDC, idempotency, and the operational tradeoffs.
Practical distributed transactions: why 2PC rarely fits, sagas (orchestration vs choreography), outbox + CDC, idempotency, and the operational tradeoffs.
URL shortener design: base62 keys, ID generation strategies, caching, analytics fanout, and how to handle a viral link gracefully.
Distributed counter at every scale. Postgres single-row up to ~10k updates/sec. Redis sharded counters up to ~1M. Async aggregation patterns for billions.
Multi-region patterns: per-tenant region pinning, read replicas everywhere, write to home region, eventual consistency on the global plane, and the operational realities.
Designing distributed locks. Redlock vs Redis SET NX, Postgres advisory locks, ZooKeeper / etcd, fencing tokens, and the patterns that prevent split-brain.
End-to-end design for a distributed cache. Consistent hashing, replication, eviction policies, hot keys, and the operational realities.
When single-Redis stops being enough. Sharded rate limiters, hybrid local/global counters, sliding-window approximations, fairness, and the patterns from CDN-scale services.
The resilience patterns every backend engineer should reach for: circuit breakers, bulkheads, backpressure, deadlines, jittered retries, and the production tradeoffs.
End-to-end system design for a distributed task queue. Durability, ordering, retries, dedup, fairness, scheduling, dead-letter handling, and the implementation patterns on Postgres, Redis, NATS, or Kafka.
A complete system design for a ride-hailing platform. Geohash / S2 / H3 indexing, real-time location ingestion, dispatch matching algorithms, ETA prediction, surge pricing, and the operational realities at scale.