Resilience strategies to level up your workloads
summary
Defines resilience as measurable RTO/RPO and nines, warns that most systems survive with single-Region multi-AZ design but some require multi-Region tradeoffs; explains Resilience Hub for automated assessments and remediation, and Fault Injection Simulator for chaos tests; compares patterns: regional sharding, single-writer with asynchronous replication, synchronous dual-writes, and DynamoDB global replication; cites a Vanguard three-Region Follow‑the‑Sun deployment; highlights pre‑provisioned capacity, control/data‑plane distinctions, and operational readiness.
AI-written summary · about
chapters (8)
- 0:00Introduction to resilience
- 1:35Key resilience concepts
- 7:03Fault isolation boundaries
- 11:01Static stability in systems
- 14:54Multi-Region design fundamentals
- 20:44Multi-Region architecture patterns
- 25:27Extreme automation tools
- 28:42Final takeaways and conclusion
related talks
55mEngineer application resilience with compliance in mind
32mResiliency and Availability Design Patterns for the Cloud
35mDesign patterns for application resiliency
42mImplementing resiliency with Cloud Operations
53mResiliency and Availability Design Patterns for the Cloud
51mPatterns for building resilient software systems
44mFrom here to resilience - a travel guide
40mThe Art of Embracing Failure at Scale