Automating Disaster Recovery: The Ultimate Reliability Challenge
summary
Claims day Zero reliability is required and shows a pragmatic patch: Cisco automates cross‑region recovery for 215 services by shipping a standby data copy, scripting promotion steps into YAML failover recipes and running them on a platform framework built by platform engineers for developers, leveraging Kubernetes primitives like rollbacks, scaling and draining. Result is a repeatable five minute cross-region failover in practice, acknowledged as effective but imperfect and born from retrofitting rather than redesign.
AI-written summary · about
chapters (7)
- 0:00Automating system recovery
- 5:22Reliability not an afterthought
- 10:02Ultimate reliability challenge
- 13:55Generic mitigations
- 17:50Moving workloads between regions
- 20:17Patchwork disaster recovery solution
- 23:27Reliability as day-zero concern
related talks
16mResilient by Design: Architectures for Crisis Response & Recovery
32mSchroedingers Backup
23mDressing to the 9s
14mExpect the unexpected: Building resilience with AWS
14mDisaster Recovery preparedness
16mEngineering Failure-Resilient Systems
51mDesigning for Failure: Build Resilient Services
01h 00mApplication resilience in Kubernetes... certainty even before your DRP?
