Disaster Recovery and Contingency Planning for Platforms
summary
Platform runs over 20 applications with a smaller-scale DR environment mirroring web and database tiers and a proxy/redirect server for traffic steering. Contingency exercises run quarterly/biannual/annual, define RTOs and SLO/SLA thresholds, and trigger failover when requests exceed 45 seconds or when an agreed failure rate hits a threshold (optionally split traffic 50/50). Document exact roles, step-by-step failover and failback tasks, automate preliminary resource scaling, and validate via stakeholder regression testing before returning to primary.
AI-written summary · about
related talks
14mThe Multi‑Workload Challenge: Predictable Failover
13mBuilding Resilient Emergency Response Platforms
14mDisaster Recovery preparedness
25mAutomating Disaster Recovery: The Ultimate Reliability Challenge
01h 00mApplication resilience in Kubernetes... certainty even before your DRP?
38mRunning DRP Tabletop Exercises
27mState of the Union on Disaster Recovery
47mBuilding Resilience