The art of being resilient. How to handle failures gracefully in Distributed Systems.
summary
Shows how structured logging (JSON metadata + common schema) and propagated headers for Jaeger traces let teams pinpoint the failing microservice and cut MTTR dramatically; demonstrates using queuing/throttling, feature flags and sidecar proxies (Envoy/Istio) to apply circuit breakers without changing app code; recommends Resilience4j/Sentinel for in-code fallbacks, defines service-level indicators/objectives to drive alerts, and links to a runnable demo that exercises these patterns end to end.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:23Distributed Architecture
- 6:20Detecting Bad Behavior
- 7:18Problem Perspective
- 9:00Structured Logging
- 13:20Observability
- 17:05Control Switches
- 24:30SLX
- 26:45Summary
related talks
55mGoing Resilient
50mSurviving Scale: Patterns for Evolving Failure-Resilient Microservices
37mResilience Design Patterns
44mIs Resilience4j enough to make fault tolerant software?
31mDesigning for failure
53mResiliency and Availability Design Patterns for the Cloud
35mDesign patterns for application resiliency
49mImproving Observability of Distributed Systems