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
Engineering Large Systems When You're Not Google Or Facebook (test in prod)
Search
Charity Majors
April 30, 2018
Technology
20
5.4k
Engineering Large Systems When You're Not Google Or Facebook (test in prod)
lightning talk at Clever, 4/30/18
Charity Majors
April 30, 2018
Tweet
Share
More Decks by Charity Majors
See All by Charity Majors
Case Studies: Modern Development Practices In Highly Regulated Environments
charity
3
3.5k
Compliance & Regulatory Standards Are NOT Incompatible With Modern Development Best Practices
charity
7
5.3k
Perils, Pitfalls and Pratfalls of Platform Engineering (QCon NYC, 2023)
charity
0
240
The Death of DevOps Has Been Greatly Exaggerated, but Platform Engineering Is Here To Stay
charity
1
300
The Future of Ops Jobs (PlatformCon 2023)
charity
2
130
Observability and the Glorious Future (with Liz Fong-Jones)
charity
0
230
The Engineer/Manager Pendulum (QCon SF 2022)
charity
0
820
Being On Call Does Not Have to Suck.
charity
1
1.2k
The Paradox of Alerts
charity
5
6.7k
Other Decks in Technology
See All in Technology
Google Cloud Next '24 Recap in ZOZO AIにより変わる開発 運用/Development and operation changed by AI
gachimuchiengineer
0
200
技術力の伸ばし方を考える
khirata
0
140
Real World Type Puzzle and Code Generation
yukukotani
4
640
データ基盤を支える技術
chanyou0311
5
3k
動画配信サービスのフロントエンド実装に学ぶ設計原則
yud0uhu
1
130
サービス開発におけるVue3とTypeScriptの親和性について
tsukuha
10
1.8k
#phpconkagawa レガシーコードにもオブザーバビリティを 〜少しずつ始めるサービス監視〜
yamato_sorariku
0
550
LINEヤフーのウェブアクセシビリティ
lycorptech_jp
PRO
2
170
1Q86
kawaguti
PRO
2
190
.NET GraphQL Client のリアル
sansantech
PRO
1
260
Autonomous Database Cloud 技術詳細 / adb-s_technical_detail_jp
oracle4engineer
PRO
15
36k
シンプルなHITL機械学習と様々なタスクにおけるHITL機械学習
naohachi89
0
320
Featured
See All Featured
A Modern Web Designer's Workflow
chriscoyier
689
190k
Creatively Recalculating Your Daily Design Routine
revolveconf
211
11k
No one is an island. Learnings from fostering a developers community.
thoeni
16
2.1k
How to train your dragon (web standard)
notwaldorf
75
5.2k
5 minutes of I Can Smell Your CMS
philhawksworth
199
19k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
228
16k
Bash Introduction
62gerente
605
210k
Ruby is Unlike a Banana
tanoku
96
10k
Mobile First: as difficult as doing things right
swwweet
217
8.6k
Visualization
eitanlees
137
14k
A designer walks into a library…
pauljervisheath
201
23k
Large-scale JavaScript Application Architecture
addyosmani
504
110k
Transcript
Engineering Large Systems When You’re Not Google Or Facebook Some
Advice By Charity Majors
None
I blame this guy: Testing in production has gotten a
bad rap.
None
how they think we are how we really are
but *why*?
monitoring => observability known unknowns => unknown unknowns LAMP stack
=> distributed systems
“Complexity is increasing” - Science
Many catastrophic states exist at any given time. Your system
is never entirely ‘up’
We are all distributed systems engineers now the unknowns outstrip
the knowns why does this matter more and more?
Distributed systems are particularly hostile to being cloned or imitated
(or monitored). (clients, concurrency, chaotic traffic patterns, edge cases …)
Distributed systems have an infinitely long list of almost-impossible failure
scenarios that make staging environments particularly worthless. this is a black hole for engineering time
unit tests integration tests functional tests basic failover test before
prod: … the basics. the simple stuff. known-unknowns
behavioral tests experiments load tests (!!) edge cases canaries rolling
deploys multi-region test in prod: unknown-unknowns
test in staging? meh
unit tests integration tests functional tests “What happens when …”
(you know the answer) “What happens when …” (you don’t) behavioral tests experiments load tests (!!) edge cases canaries rolling deploys multi-region test before prod: test in prod:
Only production is production. You can ONLY verify the deploy
for any env by deploying to that env
1. Every deploy is a *unique* exercise of your process+
code+system 2. Deploy scripts are production code. If you’re using fabric or capistrano, this means you have fab/cap in production.
Staging is not production.
Why do people sink so much time into staging, when
they can’t even tell if their own production environment is healthy or not?
That energy is better used elsewhere: Production. You can catch
80% of the bugs with 20% of the effort. And you should. @caitie’s PWL talk: https://youtu.be/-3tw2MYYT0Q
feature flags (launch darkly) high cardinality tooling (honeycomb) canary canary
canaries, shadow systems (goturbine, linkerd) capture/replay for databases (apiary, percona) also build or use: plz dont build your own ffs
Failure is not rare Practice shipping and fixing lots of
small problems And practice on your users!!
Failure: it’s “when”, not “if” (lots and lots and lots
of “when’s”)
Does everyone … know what normal looks like? know how
to deploy? know how to roll back? know how to canary? know how to debug in production? Practice!!~
None
None
None
• Charity Majors @mipsytipsy