
We keep spare infrastructure running for the worst day of the year. It consumes resources every other day. We wanted to know how much standby capacity we actually need to buy the recovery objective we promise.
We built the same Kubernetes service with three disaster recovery strategies: pilot light, warm standby, and hot standby. Then we failed the primary region and measured what happened.
The tradeoff was visible on both sides. Keeping more capacity ready reduced recovery time, but increased energy use while waiting for an incident. Keeping less capacity idle saved energy, but made recovery depend on provisioning, autoscaling, cache warming, and downstream capacity exactly when the system was already under stress.
We'll compare each strategy using recovery time, p99 latency, failed requests, error budget burn, and workload energy measured during both idle and recovery periods. We will also look at where scaling from a smaller standby stops being fast enough to satisfy the RTO.
We'll finish with a practical method for sizing standby capacity from an RTO instead of assuming that more redundancy is always better.
Manan Chawda is a software engineer at Experian focused on distributed systems, cloud-native platforms, and production reliability. He has built backend and data infrastructure across AdTech and FinTech and holds an M.S. in Computer Science from New York University. Nikunj Doshi makes Solutions simpler, secured, reliable and accessible. Nikunj Doshi is an accomplished IT Architect with over 10+ years of professional experience and more than a decade of deep specialization in Open Source technologies, Cloud Architecture, Artificial Intelligence, and Cybersecurity. His career reflects a rare combination of technical excellence, research contribution, global project leadership, and sustained community impact.