Minimal Viable Resiliency - Invest Iteratively in Reliability & Observability
summary
Framework shows five concrete resiliency levels and claims level three is the recommended Minimum Viable Resiliency because it delivers the best ROI: monthly failovers, automated critical-dependency tests, production chaos experiments only after readiness, and defined fallbacks for top workflows. Implementation uses CI/CD gates, dashboards, game days and autoscaling; estimated cost curve peaks at level three (one–three engineers monthly) then falls. Success is measured by confidence metrics — mean revenue lost per incident, customer-impact duration, fallback enable time and failover time.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:01Resilient Superior performance Scalable design Portable Compliant & Secure
- 8:26Resiliency testing Deployment model Monitoring metrics
- 12:43Network VM infra Load balancer Failover Capacity Cold start
- 13:55Networking Redundancy Hardware Redundancy Geographic Redundancy Scaling policies Application Fallbacks
- 30:39Mean Revenue Loss per Incident Average Customer Impact Duration Mean Time to Enable Fallbacks Gracefully Variance in Response time Average Time to Failover
related talks
58mResilient by Design
25mBuilding a highly scalable system to assure Business Resilience
49mResilience As A Continuous Delivery Enabler
51mWithout Resilience, Nothing Else Matters
37mReactive to Proactive Continuous Resilience
22mResilience Is Not Enough
16mResilient by Design: Architectures for Crisis Response & Recovery
22mA Reliability Maturity Model Explained
