Reliability for All of Us
summary
Talk outlines practical reliability engineering for software and infrastructure—covering networks, security, and building dependable systems to reduce on-call interruptions. It presents approaches and practices to make services more resilient and minimize manual intervention so operators can avoid frequent emergency wake-ups and nighttime firefighting.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 3:48Reliability for small teams
- 6:24Common failure causes
- 9:07Essential vs accidental complexity
- 11:17Reliable systems with boundaries
- 14:05Adopting new tools
- 17:39Separating business logic
- 20:16Minimizing dev risk
- 22:46Silent failures and feedback
- 25:19Circuit breakers for resilience
- 27:50Redundancy and diversity
- 30:23Timeouts and degradation
- 32:48Microservices and combinatorial explosions
- 35:01Error handling
- 36:33Crash-only design
- 38:19Safe failure recovery
- 40:18Resilient app principles
- 41:02Node.js reliability history
related talks
51mSoftware/site reliability of distributed systems
46mReliability Engineering
05mWhat is resilience engineering
32mPsychologically Safe Reliability Management
13mBeyond observability: Using reliability scores to drive results
17mAI-Driven Prompts for Enhanced System Reliability
47mSRE, Myths vs Realities
18mMeasuring Reliability Culture to Optimize Tradeoffs: Perspectives from an...