Outage case study9 min
Keeping copies of data on several nodes for durability and read scale.Whether every reader sees the latest write, and how soon.Staying up and correct when parts of the system fail.Services react to published events instead of calling each other.
PremiumGitHub: 43 seconds, 24 hours
October 2018. A 43-second network cut moved GitHub's databases across the country, and GitHub chose a degraded day over losing writes.
Premium
This case study is on the Premium plan
Readers with Lifetime Access read it in full. Already bought it? Sign in from the top bar.
What’s inside
- At a glance
- What users saw
- Timeline
- The root cause
- Why it spread
- How it was fixed
- Design lessons
- The interview angle
- Sources