Book · 2007
Release It!
by Michael T. Nygard
A field guide to killing your production system on purpose, in staging, before overload and cascading failures kill it for you on a Friday night.
What does Reddit think of Release It!?
Release It! has an image problem it didn't design. The ↑17 r/ExperiencedDevs comment says as much outright: 'I'll second the confusingly named Release It!. It's not about QA checklists.' What it's actually about, per that same comment, is the book that popularized the term 'circuit breaker,' now standard vocabulary in distributed systems long after most people forgot where it came from. The ↑16 comment calls it a primer for building and running services in production and, specifically, for categorizing failures, a narrower and more useful claim than generic praise. The ↑14 r/AskProgramming list frames it around stability patterns for surviving production failures, grouped with SICP as foundational rather than trendy. Recognized mentions are thin, mostly r/ExperiencedDevs, running positive throughout; there isn't enough volume here to call it a fleet-wide consensus pick, just a small, consistent group of engineers crediting it with vocabulary the field still uses.
Community feedback & reader fit
Themes
- · Popularized the term 'circuit breaker,' now standard vocabulary
- · A misleading title that undersells what's inside
- · Failure categorization as the specific, cited use case
- · Grouped with SICP as foundational reading, not a trend pick
Common praise
- + The ↑17 comment credits it with popularizing 'circuit breaker,' calling the book itself full of 'gold nuggets.'
- + The ↑16 comment calls it a primer specifically for categorizing failures in production systems, not generic advice.
- + The ↑14 r/AskProgramming list puts it next to SICP as foundational, not a passing trend recommendation.
Common criticism
- − Recognized mentions are thin across seven years, almost all from a single subreddit, so there isn't much independent confirmation here.
- − The ↑17 comment has to open by defending the title itself, 'the confusingly named Release It!,' before it can get to what the book is actually about.
Who it's for
Go here first if 'circuit breaker' is a term you use without knowing its origin; the ↑17 comment traces it back to this book directly. Want a way to think about categorizing production failures rather than just avoiding them? That's the ↑16 comment's specific pitch. Don't be thrown by the title, since even the people recommending it admit, per the ↑17 comment, that it sounds like a QA checklist and isn't one.
Mentions over time
Top subreddits
Which Reddit comments matter for Release It!?
The most relevant excerpts across the subreddits where this book is mentioned — opinionated, argued takes first, then top-upvoted mentions. Click through to read the full thread.
“ADRs are king. We use \Michael Nygard's template\ at work. The lazier devs still struggle but it made a big impact from day one.
“Here are some of my favorites, but in general writing code isn't the bottleneck as you become more senior. It is trying to understand the domain and solve their problems (often self inflicted). "Escaping the build trap" - ISBN 978-1491973790 "Learning domain driven design" - ISBN 978-1098…
“**Conferences:** - DevOpsDays - Velocity Conference - DevOps Enterprise Summit - ChefConf - PuppetConf - AWS re:Invent - Monitorama - Surge - ScaleConf - Structure - RSA - GlassCon - meetup.com **Books:** - **The Phoenix Project** - Gene Kim - The Unicorn Project - Gene Kim - **The DevOp…
“I'll second the confusingly named "Release It!". It's not about QA checklists, this is the book that popularized the concept of "circuit breaker". Lots of gold nuggets in there. The other best general book I've read in the last 20 years is Ousterhout's "Philosophy of Software Design". It's short, p…
“Release It! Design and deploy production ready software. It is a great primer on actually building and running services in production, and how to categorize failures.
“Best programming/system books suggested so far (curated order): - SICP – Structure and Interpretation of Computer Programs - Think like a computer; from first principles to building a virtual machine and compiler. - Release It! – Michael Nygard - Survive production failures; stability patterns lik…
“Systems design and distributed computing. Also this book, [Release It! Design and Deploy Production-Ready Software Second Edition](
“I think the books that had the biggest impact on me as an engineer would be: - Designing Data-Intensive Applications by Kleppmann: While it’s framed as being about data, it’s really the best overview of how modern high-scale systems that surround us work. Pairs well with Web Scalability for Softwar…
Convinced? Pick up Release It!
Readers also mention
Books that share discussion threads with Release It! — counted from the comments, not curated.
Guides featuring Release It!
Ranked best-of lists and editorial guides where this book's tracked mentions place it.
Release It! — frequently asked
What does the title Release It! actually mean?+
Less than it sounds like, per the ↑17 r/ExperiencedDevs comment, which calls it 'the confusingly named Release It!' and clarifies it's not about QA checklists. The same comment credits it with popularizing 'circuit breaker,' a core term in production resilience.
Is Release It! still relevant if I don't work on distributed systems?+
The displayed excerpts lean toward yes for anyone shipping production software. The ↑16 comment describes it as a primer for building and running services in production and categorizing failures, a general skill rather than a distributed-systems-only concern.
How does Release It! compare to SICP?+
The ↑14 r/AskProgramming list puts them side by side as foundational, SICP for thinking like a computer from first principles, Release It! for surviving production failures through stability patterns. Nothing in the excerpt ranks one over the other; they're framed as covering different ground.
Who wrote Release It!, and do they have other well-known work?+
Michael Nygard, per the ↑14 comment's attribution. The ↑69 r/ExperiencedDevs comment separately references 'Michael Nygard's template' for architecture decision records, a different, widely used artifact from the same author, though that comment isn't about Release It! itself.