Dealing With Contention medium
The Circuit Breaker pattern helps managing contention during failure by:
- A Retrying infinitely.
- B Using a bigger fuse.
- C Alerting the user.
- D Short-circuiting requests (failing fast) when a service is detected as Unhealthy, preventing the client from wasting resources waiting for timeouts and giving the service time to recover.
Answer: D. Short-circuiting requests (failing fast) when a service is detected as Unhealthy, preventing the client from wasting resources waiting for timeouts and giving the service time to recover.
It stops the 'Retry Storm' at the source.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Why is 'Exponential Backoff' preferred over constant intervals for retries?
- What is the primary purpose of a Mutex (Mutual Exclusion) lock?
- Why does adding more threads sometimes *decrease* performance?
- In a Saga, if a Compensating Transaction (Undo) fails repeatedly due to contention, what is the last resort?
- In a database, what happens if Transaction A locks a row and Transaction B tries to modify the same row?
- A database restart causes thousands of application servers to instantly try to reconnect. This crashes the DB again. This is called: