Book
The DevOps Handbook
How to Create World-Class Agility, Reliability, and Security in Technology Organizations
Gene Kim, Jez Humble, Patrick Debois, John Willis
Summary
Where The Phoenix Project dramatized the problem as a novel, this is the implementation manual. It is organized around the Three Ways — flow, feedback, and continual learning — and turns each into concrete practice: making work visible across the value stream, building a deployment pipeline that renders releases boring, wiring telemetry so failures surface before customers report them, and treating information security as part of everyone's daily work rather than a gate at the end. Much of its weight comes from the case studies, drawn from organizations that did this at scale under very different constraints, which is also the honest counterargument to reading it as a recipe. It behaves like a handbook in the literal sense: a reference you return to one practice at a time, rather than a book you finish once.
Target Readers
- Technical leaders introducing DevOps into an organization that already ships working software but does so slowly and at high risk
- Engineers designing CI/CD and automation who want the reasoning behind each practice rather than tool configuration
- Readers of The Phoenix Project looking for the implementation detail the novel deliberately left out
- Security engineers who need to embed security into a delivery pipeline instead of bolting it on at the end
Tags
Colophon
- Publisher
- Nikkei BP
- ISBN
- 978-4-8222-8548-7
- Published
- Jun 2017
- List price
- ¥3,520incl. taxMay differ from the actual selling price on Amazon
Get this book
* The link above is an advertisement via Amazon Associates.Related Books
Prerequisites
- Recommended
The Phoenix Project
A Novel about IT, DevOps, and Helping Your Business Win
Gene Kim, Kevin Behr, George Spafford
Reason: 'The Phoenix Project' lets you experience the chaos of IT operations through a novel, internalizing why DevOps is needed. Once you feel the problem, the royal road is to learn the solutions as systematic practices in 'The DevOps Handbook' by the same author team (Gene Kim et al).
- Related
The Unicorn Project
A Novel about Digital Disruption, Developers, and Overthrowing the Ancient Powerful Order
Gene Kim
Reason: After grasping the developer-side frustrations in 'The Unicorn Project', the next stage is translating them into concrete practices. 'The DevOps Handbook' covers techniques from deployment automation to feedback loops, turning the problem awareness from the novel into implementable procedures.
Next Books
- Recommended
Continuous Delivery
Reliable Software Releases through Build, Test, and Deployment Automation
Jez Humble, David Farley
Reason: Where 'The DevOps Handbook' surveys broad DevOps practices, Humble & Farley's 'Continuous Delivery' digs into its core—building deployment pipelines—as the original source. Ideal for solidifying the theoretical backbone of CI/CD after grasping the overall picture of practice.
- Recommended
Accelerate
The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations
Nicole Forsgren, Jez Humble, Gene Kim
Reason: Once you adopt practices, you want to measure whether they actually work. 'Accelerate' provides the scientific basis—grounded in DORA research—to quantify organizational performance via four metrics: deployment frequency, lead time, change failure rate, and time to restore.
- Recommended
Team Topologies
Organizing Business and Technology Teams for Fast Flow
Matthew Skelton, Manuel Pais
Reason: Even if you adopt DevOps as a technical practice, fast flow won't emerge while the org structure stays siloed. Skelton & Pais's 'Team Topologies' presents organizational design that turns Conway's Law to your advantage via four team types and interaction modes, aligning the two wheels of technology and organization.
- Recommended
Site Reliability Engineering
How Google Runs Production Systems
Betsy Beyer, Chris Jones, Jennifer Petoff, Niall Richard Murphy
Reason: Where 'The DevOps Handbook' preaches collaboration between development and operations, Google's 'Site Reliability Engineering' shows the concrete form of solving the operations side 'with software engineering'. With error budgets and SLOs to engineer reliability, it is a natural evolution of DevOps.
- Recommended
Software Engineering at Google
Lessons Learned from Programming Over Time
Titus Winters, Tom Manshreck, Hyrum Wright
Reason: After learning DevOps culture and practices in 'The DevOps Handbook', move to a concrete example of how a hyperscale organization operates them over the long term. 'Software Engineering at Google' frames engineering as 'programming integrated over time', offering insight into large-scale, long-lived engineering culture as a cross-domain bridge.