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
38
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
730
Design System Support Beyond React
jaketrent
0
650
Getting into Frontend Dev Today
jaketrent
0
620
Encourage Great Combinations
jaketrent
0
690
Getting into React
jaketrent
0
720
Ways to Compose in React
jaketrent
0
71
Anatomy of a Blot Post
jaketrent
0
67
Voice of the Leaders
jaketrent
0
66
Other Decks in Programming
See All in Programming
Processing Gem ベースの、2D レトロゲームエンジンの開発
tokujiros
2
120
CloudflareのChat Agent Starter Kitで簡単!AIチャットボット構築
syumai
1
240
Jakarta EE Core Profile and Helidon - Speed, Simplicity, and AI Integration
ivargrimstad
0
280
ライブ配信サービスの インフラのジレンマ -マルチクラウドに至ったワケ-
mirrativ
2
270
MCPでVibe Working。そして、結局はContext Eng(略)/ Working with Vibe on MCP And Context Eng
rkaga
3
250
JSONataを使ってみよう Step Functionsが楽しくなる実践テクニック #devio2025
dafujii
0
220
TDD 実践ミニトーク
contour_gara
1
260
Laravel Boost 超入門
fire_arlo
2
170
Portapad紹介プレゼンテーション
gotoumakakeru
1
130
CSC305 Summer Lecture 12
javiergs
PRO
0
130
Oracle Database Technology Night 92 Database Connection control FAN-AC
oracle4engineer
PRO
1
360
MCPで実現するAIエージェント駆動のNext.jsアプリデバッグ手法
nyatinte
7
1k
Featured
See All Featured
Fashionably flexible responsive web design (full day workshop)
malarkey
407
66k
Scaling GitHub
holman
463
140k
Building an army of robots
kneath
306
46k
Imperfection Machines: The Place of Print at Facebook
scottboms
268
13k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
16k
Principles of Awesome APIs and How to Build Them.
keavy
126
17k
The Art of Programming - Codeland 2020
erikaheidi
55
13k
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
26
3k
Build The Right Thing And Hit Your Dates
maggiecrowley
37
2.8k
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
4k
KATA
mclloyd
32
14k
Embracing the Ebb and Flow
colly
87
4.8k
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/