LEARNING JOURNEY · 9 DAYS

System design, explained with pizza.

No walls of text. No jargon first. We start with a pizza shop and map every concept to the real world. By the end, you'll never forget how these systems work.

⚡

DAY 08 / 09

The Fuse Box

🍕THE PIZZA STORY

The oven keeps tripping the fuse. Instead of calling the electrician every 5 minutes, you install a circuit breaker. After 3 trips, it stays open for 30 seconds, giving the oven a break. Then it tries again. If it works, great. If not, it opens again.

🔧THE REAL WORLD

A circuit breaker stops sending requests to a failing service. After N failures, it 'opens' and returns an error immediately. After a timeout, it 'half-opens' to test if the service recovered. Prevents cascading failures.

Circuit BreakerBulkheadRetry with BackoffFallback

⚡MEMORY HOOK — NEVER FORGET THIS

Fuse box = circuit breaker. 3 strikes = stop calling the broken service. Wait 30s = half-open test. Still broken? Stay open.

🧠QUIZ — TEST YOUR MEMORY

QUESTION 1 / 5

SCORE: 0

Your service calls the Payment API. It's down. Every request waits 30 seconds before timing out. Soon your threads are all stuck waiting. What problem is this?

FIG · DAY 08

KEY TERMS FOR DAY 08

Circuit BreakerA fuse for service calls. Trips after N failures, blocks calls, retries later.

CLOSEDHealthy state. All requests pass through normally.

OPENTripped. Fail fast — return error immediately, don't call downstream.

HALF-OPENTesting recovery. Let 1 request through; success → CLOSED, fail → OPEN.

Exp. BackoffWait longer between retries: 1s, 2s, 4s, 8s. Prevents thundering herd.

JitterRandom delay added to backoff so clients don't retry in sync.

BulkheadIsolate resources (thread pools) so one failure doesn't sink the ship.

FallbackPlan B when the call fails: cached data, default value, friendly error.

🎯 AMAZON INTERVIEW ANGLE

→"How do you stop a slow downstream service from killing your service?" → Circuit breaker + timeouts + bulkheads. Fail fast, isolate thread pools per dependency.
→"Tune the breaker for me." → Trip after ~50% errors in a 10s window with min 20 requests. Stay OPEN for 30s, then HALF-OPEN with 1 probe. (Hystrix/Resilience4j defaults.)
→"What's a thundering herd?" → 10k clients retry the EXACT same instant after an outage and DDoS the recovering service. Fix: exponential backoff + jitter.
→"Where do you place the breaker — client or server?" → On the CLIENT side, around outbound calls. Each caller decides when its dependency is unhealthy.

💡 STUDY TIP

Close your eyes and picture the pizza shop. Walk through the story in your head. If you can narrate the pizza version, you can explain the technical version. The analogy is your anchor — the jargon is just a vocabulary layer on top.