Top positive review
The definitive guide to DevOps
Reviewed in the United States on December 31, 2017
This book is a worthy sequel to The Phoenix Project, a kind of novel that illustrated the principles of DevOps in a similar fashion that Goldratt's The Goal explained a generation ago the principles behind lean manufacturing and the theory of constraints. It used a fictional story to help the reader understand the "why" of DevOps and what a successful end state looks like. In The DevOps Handbook the same set of authors continue where they left off, this time explaining the "how" of DevOps, how the three Ways (flow, feedback, continuous learning) are implemented in practice. This book lets you see through the current hype around DevOps, much of it coming from tool vendors positioning their various "solutions" as silver bullet, putting the technology in its rightful place beside people and process. While in the Flow section there is plenty on continuous integration and continuous delivery (CI/CD) that for most people is what first comes to mind when they think of DevOps, since so much has been written about this elsewhere I don't think this is the most useful part of the book. To me the most valuable section, because it's not covered so well elsewhere, is the one on the principles of feedback, how information flows back from production environments to development via telemetry and A/B testing. But perhaps what is most useful and by itself makes this book more than worth its price are the various case studies from the companies with the most mature DevOps practices, what problems they were struggling with at first and how they got to where they are now. The book ends on a great note with the appendix, which elaborates on the lean principles on which the theoretical framework behind DevOps is built, a how to guide on "blameless postmortems", and an extensive list of references, most of them with URLs, so that the reader can drill down on all the subjects covered.