A resilient application in a partially degraded world
summary
Examines how to design resilient cloud applications using AWS and Kubernetes in environments that can be partially degraded, discussing availability targets like “four nines” and the fragility introduced by APIs and microservices. Covers architectural approaches and trade-offs for maintaining high availability as systems grow more complex.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:36Nine nines availability
- 9:43Distributed degraded systems
- 14:16Observability metrics
- 18:10SLO and service contracts
- 23:33Improving resilience
- 31:40Cache and randomness
- 35:12Retries and degraded mode
- 40:26Chaos engineering resilience
- 41:52Cloud limits
- 43:37Conclusion
related talks
49mPatterns for resilient, highly available cloud architectures
53mResiliency and Availability Design Patterns for the Cloud
01h 03mPatterns for Resilient Architecture
44mBuilding resilient applications in multi-cloud
45m⚡A Resilient Application in a Partially Degraded World ⚡
32mResiliency and Availability Design Patterns for the Cloud
35mDesign patterns for application resiliency
55mGoing Resilient