Resilience Design Patterns
summary
Translates climbing anchors to software: use SERENE (Solid, Redundant, Equalized, No extension) so critical services are duplicated, load balanced and avoid cascading failures. Gives concrete failures: a hard-coded demo mode that silences submissions, an SMTP flood that knocks out alerts, and a single shared DB causing mass retries. Recommends patterns and tools: circuit breaker to trip/reset failing resources and pub/sub queues to decouple cashier/barista style services; applies PID-style control for autoscaling decisions.
AI-written summary · about
chapters (13)
- 0:00Intro
- 5:05Regulatory Information
- 6:25Demo Mode
- 8:03Redundancy
- 8:50Equalization
- 10:10No Extension
- 11:18Email Alert
- 13:01cascading failures
- 14:32high power surge
- 16:05critical resource
- 19:19real world example
- 25:07closedloop feedback
- 29:13fire alert
related talks
51mPatterns for building resilient software systems
35mDesign patterns for application resiliency
53mResiliency and Availability Design Patterns for the Cloud
55mGoing Resilient
01h 03mPatterns for Resilient Architecture
50mSurviving Scale: Patterns for Evolving Failure-Resilient Microservices
29mResilient by Design
31mDesigning for failure