Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Distributed Failure: Learning Lessons From Avia...
Search
Andrew Godwin
April 24, 2018
Programming
2
460
Distributed Failure: Learning Lessons From Aviation
A talk I first gave at Code Europe Warsaw, spring 2018.
Andrew Godwin
April 24, 2018
Tweet
Share
More Decks by Andrew Godwin
See All by Andrew Godwin
Reconciling Everything
andrewgodwin
1
280
Django Through The Years
andrewgodwin
0
170
Writing Maintainable Software At Scale
andrewgodwin
0
410
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
330
Async, Python, and the Future
andrewgodwin
2
630
How To Break Django: With Async
andrewgodwin
1
700
Taking Django's ORM Async
andrewgodwin
0
690
The Long Road To Asynchrony
andrewgodwin
0
620
The Scientist & The Engineer
andrewgodwin
1
730
Other Decks in Programming
See All in Programming
Visual StudioのGitHub Copilotでいろいろやってみる
tomokusaba
1
230
コードを読んで理解するko build
bells17
1
120
Amazon Bedrockマルチエージェントコラボレーションを諦めてLangGraphに入門してみた
akihisaikeda
1
180
高セキュリティ・高耐障害性・サブシステム化。そして2億円
tasukulab280
1
330
Domain-Driven Design (Tutorial)
hschwentner
13
22k
CIBMTR振り返り+敗北から学ぶコンペの取り組み方反省
takanao
1
220
読まないコードリーディング術
hisaju
1
140
PRレビューのお供にDanger
stoticdev
1
250
Djangoにおける複数ユーザー種別認証の設計アプローチ@DjangoCongress JP 2025
delhi09
PRO
4
520
バッチを作らなきゃとなったときに考えること
irof
2
560
コミュニティ駆動 AWS CDK ライブラリ「Open Constructs Library」 / community-cdk-library
gotok365
2
260
はじめてのIssueOps - GitHub Actionsで実現するコメント駆動オペレーション
tmknom
4
790
Featured
See All Featured
Typedesign – Prime Four
hannesfritz
41
2.5k
Docker and Python
trallard
44
3.3k
Facilitating Awesome Meetings
lara
53
6.3k
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.2k
Fontdeck: Realign not Redesign
paulrobertlloyd
83
5.4k
What's in a price? How to price your products and services
michaelherold
244
12k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
44
7.1k
Testing 201, or: Great Expectations
jmmastey
42
7.2k
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
3.7k
Making the Leap to Tech Lead
cromwellryan
133
9.1k
Keith and Marios Guide to Fast Websites
keithpitt
411
22k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
251
21k
Transcript
DISTRIBUTED FAILURE Andrew Godwin @andrewgodwin Learning lessons from aviation
Hi, I’m Andrew Godwin
Content Warning Aviation accidents Road accidents Discussion of death
Software is difficult.
Distributed is even harder.
None
Not unique to distributed systems
None
Who's solved this? Aviation.
A Boeing 747 has six million parts
A Boeing 747 has six million parts
Airplane Car Walking Train 220 130 30.8 Deaths per billion
hours (UK 1990-2000) 30
People matter as much as machines
Pilot 76% Aviation Accident Causes (2005 Nall report) 9% Other
16% Mechanical
Let's look at some aviation principles
Principle #1 Hard Failure
If something is wrong it turns itself off
This only works if you have redundancy
None
These are great ways to ensure you never fix something.
No accident or outage has a single cause. Stop your
code getting into odd states.
None
Single points of failure can be good
None
Principle #2 Good Alerting
Cockpits are incredibly selective about what sets off an audio
alarm
Alert fatigue is real. Avoid at all costs.
Never, ever, put all errors in the same place
Critical Normal Background
Critical Normal Background Wakes someone up. Actionable.
Critical Normal Background Wakes someone up. Actionable. Fixed over the
next week.
Critical Normal Background Wakes someone up. Actionable. Fixed over the
next week. Metrics, not errors.
Have you been ignoring an error for weeks? Then turn
off its error reporting.
Principle #3 Find your limits
Everything will fail. You should know when.
Copyright Boeing
What's your Minimum Equipment List?
REQUIRED OPTIONAL
Did you load test? Did you fuzz test?
You don't have to perfectly scale.
Risk is fine when you're informed!
Principle #4 Build for failure
No single thing in an aircraft can fail and take
it down.
We all want this for our code, but the way
to do it is to build for failure.
Kill your application randomly Practice server network failures Develop on
unreliable connections
The majority of pilot training is handling emergencies.
None
Use checklists. Don't rely on memory.
If you practice failure, you'll be ready when the inevitable
happens.
Pilot 76% Aviation Accident Causes (2005 Nall report) 9% Other
16% Mechanical
Principle #5 Communicate well
Distributed software means separate teams.
As you grow, communication becomes exponentially harder.
None
None
None
Clear communication is vital.
Write everything down.
Have a clear chain of command.
Make decisions.
Principle #6 No blame culture
How do I know all these aviation stats?
Every incident is reported and investigated.
There is never a single cause of a problem.
Make it very difficult to do again.
None
None
Encourage reporting.
Reward maintenance as well as firefighting
None
In aviation, every rule is written in blood.
Software is not yet there. But we are getting closer.
Margaret Hamilton Her error detection code saved Apollo 11
Therac-25 Killed 3, severely injured at least 3 more
None
None
Hard failure Good alerting Find your limits Build for failure
Communicate well No blame culture
Thanks.