Chaos Engineering for Cloud native Apps
summary
Explains how to use Azure Chaos Studio and AWS Resiliency Hub to run repeatable fault injections, with a live DR demo that shuts down one VM for five minutes while Traffic Manager routes users to the paired region and the experiment auto-rolls back. Covers concrete resiliency patterns—retry with exponential backoff, circuit breaker, bulkhead, backpressure—and infrastructure choices (multi-AZ, active‑passive, active‑active, async replication). Cites the cost of high SLAs (four nines ≈ 52 minutes/year) and CI/CD integration for continuous resiliency scoring.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 1:03Chaos engineering overview
- 5:35Resiliency fundamentals and goals
- 7:21Infrastructure resiliency patterns
- 11:54Application-level resiliency patterns
- 15:02Chaos engineering tools and steps
- 19:13Demo disaster recovery test
- 23:25Key takeaways and best practices
related talks
39mResilience & Chaos Engineering in the Cloud
57mResilient Cloud Architecture Design Patterns
48mResiliency and Availability Design Patterns for the Cloud
22mCloud-Native Apps, recovery ready!
51mAchieving Resiliency With A Multi-Cloud Or Multi-Region Approach
14mExpect the unexpected: Building resilience with AWS
48mTesting The Cloud
46mChaos Experiments - Datacenter Stress Testing