Interview › Databases & Caching
How do you handle connection storms against the cache after a deploy?
Databases & Caching · Advanced level
Answer
Connection storms happen when many clients reconnect simultaneously after deploy, failover, scaling, or network issues. I prevent them with pool caps, rolling deploys, jittered startup, exponential backoff, and readiness gates.
Technical explanation
Pods, functions, or clients can all reconnect at once and exceed DB/cache limits.
Backoff with jitter and pool caps prevent synchronized retries.
Rolling deploy settings and readiness probes must not hammer dependencies.
Hands-on example
Kubernetes guardrails:
maxSurge: 10%
maxUnavailable: 0
DB_POOL_MAX=10
REDIS_POOL_MAX=20
CONNECT_BACKOFF_JITTER=true
Add random startup sleep before opening warm connections.
Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.
More Databases & Caching interview questions
- What is Amazon RDS, and what does it manage for you versus self-managed databases?
- What database engines does RDS support?
- What is the difference between RDS and Aurora?
- What is Multi-AZ in RDS, and how does automatic failover work?
- How long does an RDS Multi-AZ failover typically take, and what triggers it?
- What is the difference between Multi-AZ and a read replica?
- When would you use a read replica, and can it become a standalone database?
- Can a read replica be in a different region, and why would you do that?