Track · Coordination & failure
Distributed Systems
Everything that changes once work spans more than one process: locks that must survive restarts, retries that must be idempotent, and failures that are only ever partial.
- Guides
- 3
- Sub-topics
- 3
- Diagrams
- 28
Sub-topic
Consistency & concurrency control
Optimistic and pessimistic control, isolation and distributed locks.
Open sub-topic-
Distributed Systems
Concurrency Control in Distributed Systems
Why local locks stop working the moment you scale past one instance, and how optimistic and pessimistic concurrency control pick up the slack — with isolation levels, lock types, and working Spring/JPA code.
-
Backend
Backend Under Load: Eight Failure Modes
A system design interview field guide to how backends actually degrade — connection pool saturation, cache stampedes, lock contention, hot partitions, slow queries, network bottlenecks, and GC pauses — plus how they cascade into each other in a real incident.
-
System Design
Distributed Systems & Backend Patterns
60+ patterns that keep production systems alive under failure, load, and scale — resilience, load management, caching, messaging, databases, distributed coordination, traffic routing, reliability, scalability, security, and observability.