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
Release It!
Search
Jake Trent
August 18, 2009
Programming
0
28
Release It!
I read this book by Michael Nygard, and here are some of my takes.
Jake Trent
August 18, 2009
Tweet
Share
More Decks by Jake Trent
See All by Jake Trent
How We Make The Design System
jaketrent
4
1.4k
Accessibility in the Pluralsight Design System
jaketrent
0
710
Design System Support Beyond React
jaketrent
0
640
Getting into Frontend Dev Today
jaketrent
0
600
Encourage Great Combinations
jaketrent
0
550
Getting into React
jaketrent
0
700
Ways to Compose in React
jaketrent
0
57
Anatomy of a Blot Post
jaketrent
0
51
Voice of the Leaders
jaketrent
0
38
Other Decks in Programming
See All in Programming
GraphQLサーバの構成要素を整理する #ハッカー鮨 #tsukijigraphql / graphql server technology selection
izumin5210
4
800
はてなにおける CSS Modules、及び CSS Modules に足りないもの / CSS Modules in Hatena, and CSS Modules missing parts
mizdra
6
880
スクラムガイドのスプリントレトロスペクティブを改めて読みかえしてみた / Re-reading the Sprint Retrospective Section in the Scrum Guide
mackey0225
3
400
GitHub Copilotのススメ
marcy731
0
190
ゆるい個人開発のススメ
kuroppe1819
10
970
Rethinking UI building strategies @ SFI 2024
letelete
0
270
PHPはいつから死んでいるかの調査
chiroruxx
1
340
Git Rebase
bkuhlmann
11
1.6k
Amazon SQSコンシューマー疎結合への旅 - 出張! #DevelopersIO IT技術ブログの中の人が語る勉強会 #3
quiver
0
210
Prepare for Jakarta EE 11 - Performance and Developer Productivity
ivargrimstad
0
670
大規模Reactアプリのリアーキテクチャ~8万行のTanStack Query移行の軌跡~
kj455
4
920
#phpcon_odawara オープン・クローズドなテストフィクスチャを求めて / open closed test fixtures
77web
3
220
Featured
See All Featured
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
124
32k
Build The Right Thing And Hit Your Dates
maggiecrowley
23
2k
Creatively Recalculating Your Daily Design Routine
revolveconf
209
11k
Mobile First: as difficult as doing things right
swwweet
216
8.6k
Building Adaptive Systems
keathley
30
1.9k
Gamification - CAS2011
davidbonilla
76
4.6k
Scaling GitHub
holman
457
140k
A Tale of Four Properties
chriscoyier
150
22k
KATA
mclloyd
14
12k
It's Worth the Effort
3n
180
27k
The Cult of Friendly URLs
andyhume
74
5.7k
Designing for Performance
lara
601
67k
Transcript
Release It! Design and Deploy Production-Ready Software Jake Trent 18
Aug 2009 by Michael T. Nygard
The Book Is thoughtful reading •Prompt evaluation: ◦Self ◦Project ◦Company
•Pragprog.com
Motivation For quality, production-ready software •Go home at night w/o
calls to your cell phone •Avoid un-needed cost: ◦Down time costs ◦Opportunity costs ◦Operational costs ◦Legal costs •Respectable work
The Need For periodic reminder of these issues •Code that
passes QA: ◦Can still fail miserably ◦Can still give users bad impressions ◦Can still inflict avoidable costs •Problems will happen
Stability Antipatterns
Integration Points Antipattern •Modern display of coupling: Systems talking to
systems •Every contact point is a possible failure point •Things not under your control ◦Network reliability ◦Data availability ◦External system correctness
Chain Reactions Antipattern •One failure often triggers another •Resource availability
often the catalyst •Turn into the system attacking itself
Cascading Failures Antipattern •Failure in one layer causes problems in
callers •Insufficiently paranoid integration points
Users Antipattern •"Users of a system have this knack for
creative destruction." •Each user consumes more memory •Some are a burden, others plain malicious
Blocked Threads Antipattern •"Adding complexity to solve on problem creates
the risk of entirely new failure modes." •Resource pool contention •Beware 3rd party API •Timeouts
Attacks of Self-Denial Antipattern •Plan for your own success •"Good
marketing can kill you at any time."
Scaling Effects Antipattern •Horizontal scale communication •Shared resource bottleneck
Unbalanced Capacities Antipattern •Performance will depend on your most constrained
resource •Not often discovered by QA •Consider proportions of types of transactions
Slow Responses Antipattern •Better to fail fast than to hog
resources only to eventually fail
SLA Inversion Antipattern •"When calling third parties, service levels only
decrease." •Consider real need and real cost •Service level can only be as high as the lowest subsystem
Unbounded Result Sets Antipattern •Test uses unrealistically small data sets
•Use limits on all queries
Stability Patterns
Use Timeouts Pattern •Prevent integration points from becoming blocked threads
•Retry for potential transient timeouts •Ability to move on without return (fail fast)
Circuit Breaker Pattern •Prevent operations rather than re-execute them •Note
each failure until switch is flipped •Use with timeouts - try again eventually •Visible to operations
Bulkheads Pattern •Find natural partitions ◦Thread groups ◦Resource pools ◦Hardware
Steady State Pattern •System should run w/o manual intervention •Human
fiddling leads to error •Purge data •Roll logs •At least move out of production environment
Fail Fast Pattern •Check availability before attempted use •Basic parameter
checking before loading expensive objects •"Don't do useless work"
Handshaking Pattern •Allow integration points to throttle themselves
Test Harness Pattern •Box independent of the "norms" of the
environment •As devious as possible, esp at network level •Out-of-spec •Stress
Decoupling Middleware Pattern •Decide on the plumbing at the "last
responsible moment" •Hardest to change later
"Paranoia is just good thinking." "It's unlikely that anyone will
notice your system's lack of downtime." Michal T. Nygard
Das Ende aprilandjake.com/content/release-it-stability-review/