Resilient by Design: Architectures for Crisis Response & Recovery
summary
Claims concrete outcomes and methods: insists on 99.99% availability, ability to absorb 10x capacity in minutes, and measurable faster recovery times. Describes tooling and patterns: Kubernetes for orchestration, Infrastructure as Code, circuit breakers, retries with exponential backoff, bulkhead isolation, multi‑region replication and intelligent traffic steering. Adds AI for predictive analytics and decision support, edge nodes <100 ms for local continuity, and a zero trust stack of continuous verification, least privilege, and ubiquitous encryption plus a phased migration plan.
AI-written summary · about
chapters (11)
- 0:00Introduction to Cloud Native Resilience
- 0:48The Need for Resilient Infrastructure
- 1:48Three Pillars of True Resilience
- 3:13Building Resilience with Cloud Native Architectures
- 4:24Distributed Resilience Patterns
- 5:37Elastic Scaling and High Availability
- 7:52AI and Edge Computing in Crisis Response
- 9:58Zero Trust Security Model
- 11:01Phased Migration to Resilient Infrastructure
- 11:52Collaborative Governance and Strategic Outcomes
- 13:43Conclusion: The Future of Resilient Infrastructure
related talks
58mResilient by Design
16mEngineering Failure-Resilient Systems
10mDesigning for Failure using AWS: Resilient Systems
51mWithout Resilience, Nothing Else Matters
22mResilience Is Not Enough
19mArchitecting Resilient Multi-Cloud Infrastructure
25mBuilding a highly scalable system to assure Business Resilience
57mResilient Cloud Architecture Design Patterns