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
480
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
310
Django Through The Years
andrewgodwin
0
200
Writing Maintainable Software At Scale
andrewgodwin
0
440
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
350
Async, Python, and the Future
andrewgodwin
2
660
How To Break Django: With Async
andrewgodwin
1
720
Taking Django's ORM Async
andrewgodwin
0
720
The Long Road To Asynchrony
andrewgodwin
0
650
The Scientist & The Engineer
andrewgodwin
1
760
Other Decks in Programming
See All in Programming
Select API from Kotlin Coroutine
jmatsu
1
180
PHP 8.4の新機能「プロパティフック」から学ぶオブジェクト指向設計とリスコフの置換原則
kentaroutakeda
1
310
Benchmark
sysong
0
230
都市をデータで見るってこういうこと PLATEAU属性情報入門
nokonoko1203
1
550
Java on Azure で LangGraph!
kohei3110
0
160
複数アプリケーションを育てていくための共通化戦略
irof
10
4k
deno-redisの紹介とJSRパッケージの運用について (toranoana.deno #21)
uki00a
0
130
DroidKnights 2025 - 다양한 스크롤 뷰에서의 영상 재생
gaeun5744
3
300
Blazing Fast UI Development with Compose Hot Reload (droidcon New York 2025)
zsmb
1
100
「ElixirでIoT!!」のこれまでとこれから
takasehideki
0
370
ドメインモデリングにおける抽象の役割、tagless-finalによるDSL構築、そして型安全な最適化
knih
11
2k
ktr0731/go-mcpでMCPサーバー作ってみた
takak2166
0
170
Featured
See All Featured
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
700
YesSQL, Process and Tooling at Scale
rocio
173
14k
Fireside Chat
paigeccino
37
3.5k
Building Better People: How to give real-time feedback that sticks.
wjessup
367
19k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
30
2.1k
Visualization
eitanlees
146
16k
Measuring & Analyzing Core Web Vitals
bluesmoon
7
490
Statistics for Hackers
jakevdp
799
220k
Art, The Web, and Tiny UX
lynnandtonic
299
21k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
231
53k
Mobile First: as difficult as doing things right
swwweet
223
9.7k
KATA
mclloyd
29
14k
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.