Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Other Sellers on Amazon
+ $3.99 shipping
+ Free Shipping
+ $3.99 shipping
The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations Paperback – October 6, 2016
Frequently bought together
Customers who bought this item also bought
Customers who viewed this item also viewed
From the Publisher
The Three Ways Revisited | The DevOps Handbook
Wondering if The DevOps Handbook is for you? Authors, Gene Kim, Jez Humble, Patrick Debois and John Willis developed this book for anyone looking to transform their IT organization—especially those who want to make serious changes through the DevOps methodology to increase productivity, profitability and win the marketplace. It is the all-inclusive guide for planning and executing DevOps transformations while providing background on the history of DevOps and dozens of case studies to support DevOps principles. It also provides best practices to help organizations unite disparate teams, achieve common goals and obtain support from the highest levels of leadership.
The DevOps Handbook digs into the three foundational principles underpinning DevOps, now known as The Three Ways: Flow, Feedback, and Continual Learning and Experimentation. The DevOps Handbook follows in the footsteps of The Phoenix Project, also by Gene Kim, by offering a high-level examination of the Three Ways as the focus of Part 1 of the new book.
As the book works through the Three Ways, readers will be able to identify how high-performing companies leveraged these principles to win the marketplace. The hope is that large organizations replicate the success of high performers to execute their own successful DevOps transformations. This six-part book is rife with useful content, including:
- The resulting work from five years of collaboration and 2,000 hours of contribution between the co-authors
- More than 40 DevOps case studies, including Amazon, Etsy, Capital One, Google, Facebook, Intuit, Nationwide Insurance and many more
- More than 400 pages of DevOps applications, lessons and 'how-to’s'.
- DevOps data gathered from more than 25,000 data points.
A follow-up to The Phoenix Project which has sold 250,000 copies, The DevOps Handbook leads with DevOps history, explaining how it was derived from bodies of knowledge that span over decades, and its resulting technical, architectural and cultural practices. Once the historical foundation is laid, readers dive into the Three Ways principles. Readers will have a deeper understanding of the theory and principles that led to DevOps today. The resulting concrete principles and patterns, and their practical application to the technology value stream, are presented in the remaining chapters of the book.
We are proud to announce that The DevOps Handbook has been given the 2016 DevOps Dozen Award for 'Best DevOps Book of the Year.'
About the Author
Gene Kim is a multiple award-winning entrepreneur, the founder and former CTO of Tripwire and a researcher. He is passionate about IT operations, security and compliance, and how IT organizations successfully transform from "good to great." He lives in Portland, Oregon.
Jez Humble is an award-winning author and researcher on software who has spent his career tinkering with code, infrastructure, and product development in organizations of varying sizes across three continents. He works at 18F, teaches at UC Berkeley, and is co-founder of DevOps Research and Assessment LLC.
Patrick Debois is an independent IT-consultant who is bridging the gap between projects and operations by using Agile techniques both in development, project management and system administration.
John Willis has worked in the IT management industry for more than 30 years. He has authored six IBM Redbooks for IBM on enterprise systems management and was the founder and chief architect at Chain Bridge Systems. He lives in Atlanta, Georgia.
John Allspaw has worked in systems operations for over fourteen years in biotech, government and online media. He started out tuning parallel clusters running vehicle crash simulations for the U.S. government, and then moved on to the Internet in 1997. He built the backing infrastructures at Salon.com, InfoWorld.com, Friendster, and Flickr. He is now VP of Tech Operations at Etsy, and is the author of "The Art of Capacity Planning" and "Web Operations" published by O'Reilly.
Author interviews, book reviews, editors picks, and more. Read it now
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
The first book "The Phoenix Project" was great and did a good job showing how the silos in tech companies can work together. I was hoping this book would go either deeper in the tech tools and show how to build workflow or more employee management (culture) to bring Sales, Ops and Dev together. Instead this book self conflicting and shallow.
Example: "Myth - DevOpst Means Eliminating IT Operations or ""NoOps""". Then says.. "... the right culture norms, small teams of developer are able to quickly, safely, and independently deploy ... changes into production" That is the definition of NoOps.
It also talks about building a trusting work place where Devs are allowed to make mistakes (because they can recover from them fast) but says nothing about the human aspect of managers firing Ops people because they missed a 2am alert and it escalated to his boss.
It is also written with many absolute comments (sales talk) Like: in chapter 1 when FOCUS(ing) ON DEPLOYMENT LEAD TIME it implies all large batch work can be reduced. This ignores IT issues like conversion of big production data sets that can take weeks.
This book comes with an code to "TAKE THE DORA DEVELOP X-RAY ASSESSMENT AND SEE WHERE YOU STAND". Marc Andreessen is famously quoted as saying, "The spread of computers and the internet will put jobs in two categories: people who tell computers what to do, and people who are told by computers what to do." Or, "automate all the things" and reduce work and work force. The Answer is - Get out of OPS go back to DEV and prepare to work on small meaningless bit of code.
The one subject this book does cover that the Phoenix Project did not is SECURITY. However, this books still see the Sec group as outsiders writing tasks (after the fact), reviewing Dev code and training DevOps and creating DevOpsSec. It thinks or hopes security problems can be coded away with tools like Gauntlt.
Conclusion: If you're looking for some good quotes about why / how you / 're company should / can move faster to build a minimum viable product (MVP) in the lease amount of time by WIP-ing works not creating it.... This book is for you.
DevOps (software DEVelopment/information technology OPerationS) is a broad term which is used to refer to a large set of practices that emphasize the collaboration and communication of software developers and information technology professionals to facilitate the automation of software delivery and infrastructure changes. DevOps attempts to develop a culture and environment where building, testing and releasing software happens rapidly, frequently and more reliably. When correctly implemented in the right organization, it’s a revolutionary method.
In The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, authors Gene Kim, Patrick Debois, John Willis and Jez Humble have written a powerful manifesto detailing how DevOps can transform the enterprise IT space. The DevOps approach, which brings together development and operations teams has been gaining significant traction for the last several years.
Many IT people and developers will recoil when reading about DevOps. This is likely due to them spending their careers in the dysfunctional types of organizations that DevOps is meant to fix. The promise of DevOps is quite compelling, but it will only work where it’s fully implemented over time. As powerful a methodology as DevOps is, it is certainly no quick fix. DevOps promises speed and agility, which it indeed can deliver. But like training for a race; getting those high levels of speed and agility can’t be done overnight.
At the start of the book, the authors write of a malady far too common in corporate America. This is IT environments where a culture of fear and lack of trust prevail; where workers who make mistakes are punished, and those who make suggestions or point out problems are viewed as whistle-blowers and troublemakers. By contrast, in the perfect world of DevOps, learning is promoted and the culture is that of a high level of trust.
While the authors are highly evangelical when it comes to DevOps, they also note that it is a huge undertaking. With its own language and culture, DevOps must have the complete and absolute blessing of management to succeed.
According to the authors (ironically in my opinion) security and compliance groups are often the ones the object to the implementation of DevOps. When done correctly, DevOps is a powerful vehicle to integrate information security into enterprise operations. As noted at DevOpsSec, the challenge facing DevOps teams today however is that incorporating security into their day-to-day work is not always easy or intuitive. Security often runs one step behind or out of sync with lean DevOps teams.
While the book does not fully deal with the integrating security into DevOps, the free eBook DevOpsSec: Securing Software through Continuous Delivery is a most helpful resource.
In The DevOps Handbook, the authors provide countless case studies and quotes regarding successes. What the book makes up in breadth, it lacks in detailed and tactical directions on how to put DevOps into full implementation. For that, those considering DevOps need to use the many other books the authors reference, as the topic is far too large to cover in a single work.
With all the success stories and case studies with happy endings; it would have been nice to hear some DevOps failures and horror stories. Understanding failure modes is a powerful learning mechanism. While the authors are quite passionate, the book comes across as overly fervent at times and can be misunderstood that DevOps can’t fail. DevOps means a massive change for most organizations who choose to go down its path, in addition to complete commitment from management and staff. It’s unreasonable to think that every organization that has gone down the DevOps path has found it beneficial.
In the world of IT, there is huge and often intolerable amounts of waste and delay. There are myriad reasons why this is, often since organizations are too large and disparate, and that processes are nowhere near streamlined. For those looking to stop that trend, The DevOps Handbook is an invaluable read.
Even for those organizations that won’t be implementing DevOps in totality, there’s still plenty of good advice to glean from this book. For those that are looking to go down the DevOps path, this is the book you want to start your journey with.