What to Do When a Minute of Downtime Costs $100,000
summary
Describes techniques for making financial-transaction systems survive extreme availability requirements when a minute of downtime costs very large sums. Covers operational and architectural measures beyond development and testing—for example runbook/process changes, redundancy and failover strategies, monitoring and incident response—to raise reliability and fault tolerance under strict SLAs.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:10Downtime commandments
- 7:23Hardware failures and external services
- 8:05System reliability basics
- 9:27Deployment and rollback requirements
- 10:08Blue-green deployment
- 11:59Traffic routing between lines
- 17:22Fast parallel deployment
- 19:27Scaling under load
- 23:03Monitoring and problem detection
- 26:11Business metrics and external services
- 29:29Root cause analysis and logging
- 33:27Process standardization
- 35:17Results and outcomes
related talks
26mImprove application resilience with chaos engineering
30mZero Down Time Operations: How to Get Atleast 3 9's of Uptime
26mUptime, Mean-Time, and Ahead of Your Time
33mResilient
29mDowntime Budgets
34m"The Upside of Downtime: How to Turn a Disaster Into an Opportunity"
29mNot All Minutes Are Equal: The Secret behind SLO Adoption Failure
21mHigh Availability & Disaster Recovery for Cloud SAP Systems