Day 1 Session 3
summary
Covers concrete patterns and tools: retry policy (max retries 3, configurable max wait seconds) and storage SDK exponential backoff; implements a chaos-tested Redis by injecting faults into a C++ server and running 1,000 client attempts to validate retry behavior; shows a circuit breaker that waits ~5 minutes and allows a single-thread probe to close the circuit; documents a cloud-only outage from missing local D: breadcrumb after disk failure; cites ARM-TTK static analysis, custom resource providers, private link, and cost levers like low-priority VMs 60-80% discount and containerize LOB for ~65% savings.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:15Retry Logic
- 5:10Testing Retry Logic
- 8:20Circuit Breaker
- 10:21Uninitialized
- 13:10Resilience
- 15:43Build Blocks
- 26:08Cost Aware Programming
- 33:56Infrastructure as Code
- 39:41Custom Resource Providers
- 44:34Wrap Up
related talks
26mThe tools and techniques behind resilient systems
25mChaos Engineering for Cloud native Apps
57mResilient Cloud Architecture Design Patterns
16mPreview: Cloud Computing
06mInterview Speaker
39mResilience & Chaos Engineering in the Cloud
48mResiliency and Availability Design Patterns for the Cloud
21mSponsored Session: Fault-Tolerant Training: How We Build Rel...