What is a circuit breaker, and how does it prevent cascading failures? Mention bulkheads too.
What they are really testing: Whether you understand failing fast to protect the caller and the dependency, the breaker states (closed/open/half-open), and bulkheading to isolate resource exhaustion.
A real interview question
What is a circuit breaker, and how does it prevent cascading failures? Mention bulkheads too.
What most people say
drag me
“A circuit breaker stops calling a service when it is failing.”
Right idea but missing the mechanism (the closed/open/half-open states and failing fast) and why it matters, freeing caller resources to stop a cascade, plus bulkheads as the complementary isolation pattern.
The follow-ups they ask next
What do the open, closed, and half-open states mean?
Closed = normal, calls pass; open = tripped, calls fail fast without hitting the dependency; half-open = a trial period letting one/few calls through to test recovery, closing if they succeed.
How does a bulkhead differ from a circuit breaker?
A breaker stops calling a failing dependency; a bulkhead isolates resources (separate pools per dependency) so one slow dependency cannot consume the resources others need. They complement each other.
What the interviewer is listening for
- Explains failing fast to free caller resources
- Knows closed/open/half-open states
- Knows bulkhead resource isolation
What sinks the answer
- Only "stops calling a failed service"
- No states / no resource-exhaustion reasoning
- Unaware of bulkheads
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“A circuit breaker [stops a slow/failing dependency from exhausting the caller resources and cascading]. It [tracks failures, opens past a threshold so calls fail fast, then half-opens to test and closes on recovery]. This [frees caller resources and lets the dependency recover]. A bulkhead [isolates resources per dependency (separate pools) so one slow dep cannot sink the whole service].”
Keep going with reliability
Foundation
What is a Region versus an Availability Zone, and why does the difference matter?
Foundation
What is the difference between vertical scaling and horizontal scaling, and when would you reach for each?
Foundation
What does "highly available" actually mean, and how do you achieve it?
Foundation
Why are stateless services easier to scale and make reliable than stateful ones?
Junior
How should a service retry a failed call to a dependency, and what is a retry storm?
Junior
What is idempotency, and why does it matter for reliable distributed systems?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free