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
障害対応を起点としたもっといい開発と運用のサイクル作りのためにできること / Hatena Enginner Seminar #29
polamjag
0
180
大規模Reactアプリのリアーキテクチャ~8万行のTanStack Query移行の軌跡~
kj455
4
960
初心者のためのRubyKaigi入門/RubyKaigi Introduction
a_matsuda
2
790
Site Reliability Engineering for GMO
pyama86
8
1k
CA.swift19 恋するAIアプリ開発の裏側
oskmr
0
360
スクラムガイドのスプリントレトロスペクティブを改めて読みかえしてみた / Re-reading the Sprint Retrospective Section in the Scrum Guide
mackey0225
3
430
DMMプラットフォームがTiDB Cloudを採用した背景
pospome
8
4.1k
Ruby GitHub Packages
bkuhlmann
0
630
TCAとKMPを用いた新規動画配信アプリ 「ABEMA Live」の設計
tomu28
1
110
MetricKitで予期せぬ終了を検知する話 / Detect unexpected termination with MetricKit
nekowen
1
190
Netty Chicago Java User Group 2024-04-17
sullis
0
180
新宿ダンジョンを可視化してみた
satoshi7190
2
260
Featured
See All Featured
We Have a Design System, Now What?
morganepeng
43
6.8k
Designing for humans not robots
tammielis
248
25k
Designing with Data
zakiwarfel
96
4.8k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
40
4.4k
Rails Girls Zürich Keynote
gr2m
91
13k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
21
1.6k
How to train your dragon (web standard)
notwaldorf
73
5.2k
Fontdeck: Realign not Redesign
paulrobertlloyd
76
4.9k
Clear Off the Table
cherdarchuk
84
310k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
155
14k
It's Worth the Effort
3n
180
27k
RailsConf 2023
tenderlove
4
540
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/