We use analytics cookies.We use cookies to analyze site traffic and improve your experience.
Loading...
System Design Masterclass · Microservices Architecture
Free preview: the first 2 parts of this 17-part lesson.
Already bought the course? Sign in to read the whole lesson.
this lesson is part of
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design courseread the rest of this lesson in
System Design Masterclass
Unlock this lesson and the 751 other paid lessons
$25 once, by PayPal
See the System Design coursein Microservices Architecture
This lesson is part of the full System Design Masterclass. Unlock it along with 769 other lessons for a one-time payment.
One-time payment by card or PayPal
Get Lifetime AccessOne-time payment: UPI, card or netbanking
Get Lifetime Access18 Foundation lessons are free, no payment needed. Try them now
It is easy and good
“It is really nice and good Please join the course”
It's Black Friday. Your e-commerce platform handles 50,000 requests per second. Everything hums along beautifully. Then at 2:47 PM, the recommendation database slows down. Not crashes, just slows down.
Within 90 seconds, every service in your system is dead. Not just recommendations. search, checkout, user profiles, everything. 50,000 users see error pages. Revenue drops to zero.
This is called a cascading failure, and it is the most common way distributed systems die.
Here's why it happens:
| Time | What Happens |
|---|---|
| T+0s | Recommendation DB response time jumps from 5ms to 8 seconds |
| T+5s | Service C (recommendations) threads all blocked waiting on DB |
| T+15s | Service B (product page) threads pile up waiting on Service C |
| T+30s | Service B's thread pool is exhausted, starts rejecting ALL requests |
| T+45s | Service A () threads pile up waiting on Service B |
| T+90s | API gateway thread pool exhausted, entire platform is DOWN |
One slow database took down an entire platform. Not because it crashed, but because it was slow. Slow is worse than down, a crashed service fails immediately, but a slow service holds onto resources while everyone waits.
This is what happened to Netflix in 2011, Amazon in 2020, and Uber in 2015. Let's look at how it propagates.
The critical insight: slow responses are worse than no responses. A crashed service returns errors immediately (in milliseconds). A slow service holds threads hostage for seconds, consuming resources across the entire call chain.