advancedScale & Rate Limiting
50,000 users log in at the same second right after a popular cache key expires, and your database gets hammered. What is this called and how do you prevent it?
Tests whether you know this is a cache avalanche/stampede, and can name real mitigations like jittered TTLs or request coalescing.
This is a Pro question
Sign in, then upgrade to Pro or Power to unlock this question and the full Interview Prep bank.
50,000 users log in at the same second right after a popular cache key expires, and your database gets hammered. What is this called and how do you prevent it?