advancedScale & Rate Limiting22 of 127
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.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a responseNext Step
←PreviousContinue to How do you ensure message idempotency in an event-driven system using an event ID deduplication table?→
← Back to all Company Round Scenarios questions