Dealing With Contention medium
A database restart causes thousands of application servers to instantly try to reconnect. This crashes the DB again. This is called:
- A Lazy Loading.
- B Connection Pooling.
- C Sharding.
- D A Connection Storm (or Logon Storm).
Answer: D. A Connection Storm (or Logon Storm).
Authentication is CPU expensive. Handling 10k handshake requests at once saturates the DB CPU, preventing it from serving queries.
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?
- To save a system under extreme contention, you implement 'Load Shedding'. What is the most effective strategy?