Designing for Failure: Build Resilient Services
summary
Claims concrete steps and tools: redundancy split into infrastructure data service replicas, failover demonstrates automatic vs manual and DNS failover, graceful shutdown shows connection draining health check signaling and reasonable timeouts, chaos engineering runs controlled failure injections including simulate DB primary failure and network partitions, circuit breakers use closed open half open states and metrics like MTTR and error rate, autoscaling and rollback strategies replace unhealthy instances and restore a safe deployment.
AI-written summary · about
chapters (21)
- 0:00Introduction to Failure-Aware Design
- 2:02The Importance of Redundancy
- 3:12Infrastructure Redundancy Explained
- 4:26Data Redundancy Strategies
- 5:39Service Redundancy in Microservices
- 6:44Balancing Redundancy Costs
- 8:48Failover Mechanisms
- 9:26Automatic vs. Manual Failover
- 13:08Challenges in Implementing Failover
- 15:49Graceful Degradation
- 22:18Designing for Graceful Shutdown
- 26:51Challenges of Graceful Shutdown
- 27:27Testing Shutdown Scenarios
- 28:36Real World Examples of Graceful Shutdown
- 29:47Introduction to Chaos Engineering
- 31:29Techniques in Chaos Engineering
- 33:23Benefits of Chaos Engineering
- 34:07Challenges in Chaos Engineering
- 35:53Understanding Circuit Breakers
- 42:20Automated Recovery Mechanisms
- 49:29Key Strategies for Building Resilient Systems
related talks
10mDesigning for Failure using AWS: Resilient Systems
16mEngineering Failure-Resilient Systems
10mBuilding an 'Oops-Less Operation' at Scale
28mBuilding Resilient DevOps Pipelines: Strategies for Handling Unexpected Failures &...
50mSurviving Scale: Patterns for Evolving Failure-Resilient Microservices
16mResilient by Design: Architectures for Crisis Response & Recovery
22mResilience Is Not Enough
31mPlanning for Failure using Chaos Engineering