The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations
- Downloads：9318
- Type：Epub+TxT+PDF+Mobi
- Create Date：2021-03-11 08:11:25
- Update Date：2025-09-07
- Status：finish
- Author：Gene Kim
- ISBN：1942788002
- Environment：PC/Android/iPhone/iPad/Kindle
- Download
Summary
Increase profitability， elevate work culture， and exceed productivity goals through DevOps practices。
More than ever， the effective management of technology is critical for business competitiveness。 For decades， technology leaders have struggled to balance agility， reliability， and security。 The consequences of failure have never been greater whether it's the healthcare。gov debacle， cardholder data breaches， or missing the boat with Big Data in the cloud。
And yet， high performers using DevOps principles， such as Google， Amazon， Facebook， Etsy， and Netflix， are routinely and reliably deploying code into production hundreds， or even thousands， of times per day。
Following in the footsteps of The Phoenix Project， The DevOps Handbook shows leaders how to replicate these incredible outcomes， by showing how to integrate Product Management， Development， QA， IT Operations， and Information Security to elevate your company and win in the marketplace。"
Table of contents
Preface
Spreading the Aha！ Moment
Introduction
PART I: THE THREE WAYS
1。 Agile， continuous delivery and the three ways
2。 The First Way: The Principles of Flow
3。 The Second Way: The Principle of Feedback
4。 The Third Way: The Principles of Continual Learning
PART II: WHERE TO START
5。 Selecting which value stream to start with
6。 Understanding the work in our value stream…
7。 How to design our organization and architecture
8。 How to get great outcomes by integrating operations into the daily work for development
PART III: THE FIRST WAY: THE TECHNICAL PRACTICES OF FLOW
9。 Create the foundations of our deployment pipeline
10。 Enable fast and reliable automated testing
11。 Enable and practice continuous integration
12。 Automate and enable low-risk releases
13。 Architect for low-risk releases
PART IV: THE SECOND WAY: THE TECHNICAL PRACTICES OF FEEDBACK
14*。 Create telemetry to enable seeing abd solving problems
15。 Analyze telemetry to better anticipate problems
16。 Enable feedbackso development and operation can safely deploy code
17。 Integrate hypothesis-driven development and A/B testing into our daily work
18。 Create review and coordination processes to increase quality of our current work
PART V: THE THRID WAY: THE TECHNICAL PRACTICES OF CONTINUAL LEARNING
19。 Enable and inject learning into daily work
20。 Convert local discoveries into global improvements
21。 Reserve time to create organizational learning
22。 Information security as everyone’s job， every day
23。 Protecting the deployment pipeline
PART VI: CONCLUSION
A call to action
Conclusion to the DevOps Handbook
APPENDICES
1。 The convergence of Devops
2。 The theory of constraints and core chronic conflicts
3。 Tabular form of downward spiral
4。 The dangers of handoffs and queues
5。 Myths of industrial safety
6。 The Toyota Andon Cord
7。 COTS Software
8。 Post-mortem meetings
9。 The Simian Army
10。 Transparent uptime
Additional Resources
Endnotes
More than ever， the effective management of technology is critical for business competitiveness。 For decades， technology leaders have struggled to balance agility， reliability， and security。 The consequences of failure have never been greater whether it's the healthcare。gov debacle， cardholder data breaches， or missing the boat with Big Data in the cloud。
And yet， high performers using DevOps principles， such as Google， Amazon， Facebook， Etsy， and Netflix， are routinely and reliably deploying code into production hundreds， or even thousands， of times per day。
Following in the footsteps of The Phoenix Project， The DevOps Handbook shows leaders how to replicate these incredible outcomes， by showing how to integrate Product Management， Development， QA， IT Operations， and Information Security to elevate your company and win in the marketplace。"
Table of contents
Preface
Spreading the Aha！ Moment
Introduction
PART I: THE THREE WAYS
1。 Agile， continuous delivery and the three ways
2。 The First Way: The Principles of Flow
3。 The Second Way: The Principle of Feedback
4。 The Third Way: The Principles of Continual Learning
PART II: WHERE TO START
5。 Selecting which value stream to start with
6。 Understanding the work in our value stream…
7。 How to design our organization and architecture
8。 How to get great outcomes by integrating operations into the daily work for development
PART III: THE FIRST WAY: THE TECHNICAL PRACTICES OF FLOW
9。 Create the foundations of our deployment pipeline
10。 Enable fast and reliable automated testing
11。 Enable and practice continuous integration
12。 Automate and enable low-risk releases
13。 Architect for low-risk releases
PART IV: THE SECOND WAY: THE TECHNICAL PRACTICES OF FEEDBACK
14*。 Create telemetry to enable seeing abd solving problems
15。 Analyze telemetry to better anticipate problems
16。 Enable feedbackso development and operation can safely deploy code
17。 Integrate hypothesis-driven development and A/B testing into our daily work
18。 Create review and coordination processes to increase quality of our current work
PART V: THE THRID WAY: THE TECHNICAL PRACTICES OF CONTINUAL LEARNING
19。 Enable and inject learning into daily work
20。 Convert local discoveries into global improvements
21。 Reserve time to create organizational learning
22。 Information security as everyone’s job， every day
23。 Protecting the deployment pipeline
PART VI: CONCLUSION
A call to action
Conclusion to the DevOps Handbook
APPENDICES
1。 The convergence of Devops
2。 The theory of constraints and core chronic conflicts
3。 Tabular form of downward spiral
4。 The dangers of handoffs and queues
5。 Myths of industrial safety
6。 The Toyota Andon Cord
7。 COTS Software
8。 Post-mortem meetings
9。 The Simian Army
10。 Transparent uptime
Additional Resources
Endnotes
Reviews
Miguel Silva
，
Great book！ It would be better for me to have read it 4-5 years ago， but nonetheless it was interesting to know that I adopt or learn the principles and methodologies by trying and failing and by meeting people that helped me to understand what DevOps is and why it was born。 Hope every companies by now， even no tech companies but that use technology， are adopting this for a while or are adopting or they will be out of business very soon or at least without the best persons for the job。I enjoyed Great book！ It would be better for me to have read it 4-5 years ago， but nonetheless it was interesting to know that I adopt or learn the principles and methodologies by trying and failing and by meeting people that helped me to understand what DevOps is and why it was born。 Hope every companies by now， even no tech companies but that use technology， are adopting this for a while or are adopting or they will be out of business very soon or at least without the best persons for the job。I enjoyed reading， but because it not showed me nothing new， I gave only a 4 star。 。。。more
Diego Pacheco
，
It's a good book。 I follow and practice Lean/Agile for a long time（+10 years） and also follow and do DeVOps since 2011。 So for me， there was no news。 This good still good because endorse important things like: * Lean * Kanban （Although they talk about boards - not sure if they know real kanban） * SOA * Telemetry * Health and sanitizer practices to be able to deploy anytime * Dark canaryEven I did not learn anything new or not have insights I would recommend the book。 It's a good book。 I follow and practice Lean/Agile for a long time（+10 years） and also follow and do DeVOps since 2011。 So for me， there was no news。 This good still good because endorse important things like: * Lean * Kanban （Although they talk about boards - not sure if they know real kanban） * SOA * Telemetry * Health and sanitizer practices to be able to deploy anytime * Dark canaryEven I did not learn anything new or not have insights I would recommend the book。 。。。more
Matthew Horvat
，
This book took a long time to get to the meat of the discussion， but once it did， I couldn't put it down。 The first few chapters which seemed horribly slow at the time， made up for it as the examples for why you needed Dev-Ops they provided earlier， were used to show how they went from situations that needed help， to how they went and innovated。 This book took a long time to get to the meat of the discussion， but once it did， I couldn't put it down。 The first few chapters which seemed horribly slow at the time， made up for it as the examples for why you needed Dev-Ops they provided earlier， were used to show how they went from situations that needed help， to how they went and innovated。 。。。more
Adam
，
This book does a really good job at explaining strategies to get your software work done faster and more reliably。 I really enjoyed the case studies from real companies。 I've sl0wly been putting these ideas into practice on my team， and it's making my production deploys way less anxiety-inducing。 This book does a really good job at explaining strategies to get your software work done faster and more reliably。 I really enjoyed the case studies from real companies。 I've sl0wly been putting these ideas into practice on my team， and it's making my production deploys way less anxiety-inducing。 。。。more
Sicofonia
，
The DevOps Handbook is a high level overview on what DevOps is about and how to implement it across a typical organization。 It starts by introducing Kim's Three Ways of DevOps: Fast Flow of Work， Fast Feedback and Continual Learning and Experimentation。 It then elaborates on each "way" in subsequent parts of the book， explaining the principles behind it and giving practical examples on how such principles can be implemented。 It also draws a lot from case studies from companies such as Etsy， Amaz The DevOps Handbook is a high level overview on what DevOps is about and how to implement it across a typical organization。 It starts by introducing Kim's Three Ways of DevOps: Fast Flow of Work， Fast Feedback and Continual Learning and Experimentation。 It then elaborates on each "way" in subsequent parts of the book， explaining the principles behind it and giving practical examples on how such principles can be implemented。 It also draws a lot from case studies from companies such as Etsy， Amazon， Facebook， Google， etc。The book itself is not that technical， so I'd say it was more oriented to managers wanted to understand what DevOps is all about and the different elements that are behind this "movement"。 So readers wanting to learn how to build a deployment pipeline might be better off looking elsewhere。Personally I think the book does a good job at depicting what the philosophy behind DevOps is。 In every single organization I worked for DevOps invariably ended up being a team responsible for deployments （and its supporting code）。 This book will show you that there's more to that。From a reading perspective I did find the second half of the book a bit tedious to read， as I felt that most case studies were OK examples that were as good page fillers as anything。 It seems to be a trend in this type of books that they are filled with case studies that serve no other purpose but to make a book longer than 300 pages。All in all a good read， definitely the right book to introduce oneself to the topic of DevOps。 For concrete technical practices， like I pointed out above， look elsewhere。 。。。more
Carl
，
Read this in late 2020/early 2021 so some of the material is a bit out of date since publication in 2016。That said， this should be required reading for everyone involved in the development of software or even IT in general。 Great explanation of what modern DevOps and also why it's needed。 The book is a bit lighter on how to implement methods and technologies but since that changes every week this is not a big issue。 Although I have practiced DevOps for years now， I learned something from every c Read this in late 2020/early 2021 so some of the material is a bit out of date since publication in 2016。That said， this should be required reading for everyone involved in the development of software or even IT in general。 Great explanation of what modern DevOps and also why it's needed。 The book is a bit lighter on how to implement methods and technologies but since that changes every week this is not a big issue。 Although I have practiced DevOps for years now， I learned something from every chapter。 Highly recommended！ 。。。more
Martin
，
Too many words for very little information。 All I've read here was written earlier and shorter in books about agile and microservice architecture。 Too many words for very little information。 All I've read here was written earlier and shorter in books about agile and microservice architecture。 。。。more
Lynn
，
If you are， like me， a DevOps Engineer， or otherwise in an IT job where brushing up your DevOps knowledge is useful， this book is a good choice。 Obviously， if you're looking for a fun novel， don't pick this book。 It covers basic principles of DevOps， Continuous Integration， and Automation， with examples from companies like Google， Etsy， etc。 Clear explanation， interesting examples。 If you are， like me， a DevOps Engineer， or otherwise in an IT job where brushing up your DevOps knowledge is useful， this book is a good choice。 Obviously， if you're looking for a fun novel， don't pick this book。 It covers basic principles of DevOps， Continuous Integration， and Automation， with examples from companies like Google， Etsy， etc。 Clear explanation， interesting examples。 。。。more
João
，
A slog to read。 Felt like a long report instead of a book。 Should have been shorter， has quite a bit of repetition and explains such basic concepts as pull requests。There's not much new here unless you've been hostage of an FTP-to-prod organization and are just now figuring out there's another world out there。Still， the book's pretty thorough and I did learn a few things。 Plus， it's pretty 🤷🏼♂️。 A slog to read。 Felt like a long report instead of a book。 Should have been shorter， has quite a bit of repetition and explains such basic concepts as pull requests。There's not much new here unless you've been hostage of an FTP-to-prod organization and are just now figuring out there's another world out there。Still， the book's pretty thorough and I did learn a few things。 Plus， it's pretty 🤷🏼♂️。 。。。more
Rafael Mtz
，
Please devs and ops go read this now。 We are on a tidal change that is needed。 No more paralysis by management， no more wait 3 months to deploy to dev， strive for local to prod in hours or best in minutes。 It is possible， I've seen it， upper management must be convinced this is the best way and path we have。 Please devs and ops go read this now。 We are on a tidal change that is needed。 No more paralysis by management， no more wait 3 months to deploy to dev， strive for local to prod in hours or best in minutes。 It is possible， I've seen it， upper management must be convinced this is the best way and path we have。 。。。more
Andrew
，
A useful compilation of both technical and organizational methods on how to make things adequate。 Although it's quite an odd feeling when your organization implements a part of it all， the practices read like duh so obvious （CI）， but then there is some basic stuff on the first 40 pages which you want to paste all over the place。 A useful compilation of both technical and organizational methods on how to make things adequate。 Although it's quite an odd feeling when your organization implements a part of it all， the practices read like duh so obvious （CI）， but then there is some basic stuff on the first 40 pages which you want to paste all over the place。 。。。more
Tomasz Maj
，
A true manual with great examples， but I felt like I heard all the practices before。 It was a mindblowing book to read。
Kim
，
Mostly a refresher for me but a very concise one。 Not DevOps specific， topics span across entire product engineering。 Case studies are short yet memorable
Elwin Kline
，
Professional Development read for work。Unfortunately， after reading Gene Kim's The Phoenix Project， this book didn't really have that much new to offer。 A lot of these types of books and methodologies are created in a way to be super generalized with the goal of being a one size fits all type approach， allowing their product to impact the largest volume of potential customer base。 Bad thing about this， is when they good too far into the generalist category and it just becomes a little value adde Professional Development read for work。Unfortunately， after reading Gene Kim's The Phoenix Project， this book didn't really have that much new to offer。 A lot of these types of books and methodologies are created in a way to be super generalized with the goal of being a one size fits all type approach， allowing their product to impact the largest volume of potential customer base。 Bad thing about this， is when they good too far into the generalist category and it just becomes a little value added overall。 Things like 。。。 "Have the developers follow their product as it flows through the pipeline。" I mean， this sounds reasonable and a good idea， but it is nothing groundbreaking or noteworthy。 That's like saying， exercise， limit stress， and eat your vegetables and you will live a healthier life。 I think you get my point。The Phoenix Project was super fun and an incredibly good way to present these ideas in the format of a story。 This means of delivery was not nearly as effective。 Read The Phoenix Project instead。 。。。more
Michael Baumann
，
Need to get your software development business up an running， or fix some issues in your megacorporation？ Then this is the book for you。No really， good insights into product development and process improvement。
Tommi Tikkanen
，
In short: a good book to expand your knowledge about all the different aspects and details of DevOps。Pros• comprehensive overview -- lists a lot of different concepts• it gave me lots of new ideas• lots of examples of different companiesCons• doesn't go very deep into details about how to actually do things• not the smoothest narrative• for experienced people， there were quite many things we already knew• completely lacks self-criticismRating: 3。5 / 5， would recommend to all developers who are l In short: a good book to expand your knowledge about all the different aspects and details of DevOps。Pros• comprehensive overview -- lists a lot of different concepts• it gave me lots of new ideas• lots of examples of different companiesCons• doesn't go very deep into details about how to actually do things• not the smoothest narrative• for experienced people， there were quite many things we already knew• completely lacks self-criticismRating: 3。5 / 5， would recommend to all developers who are looking to improve efficiency and quality 。。。more
Koushal
，
Hooked on dev ops ！I have read this book after Phoenix and unicorn。 Simply brilliantly written and explained。 Will definitely try meeting this ideals
Simon Caudwell
，
The Bible of DevOpsIf you're looking to learn about DevOps， start with The Phoenix Project and / or The Unicorn Project。 Then read this book。 The Bible of DevOpsIf you're looking to learn about DevOps， start with The Phoenix Project and / or The Unicorn Project。 Then read this book。 。。。more
Viktor Malyshev
，
I love the book。 It's a predecessor for Accelerate， from the same authors and the State of DevOps。 To me， more technical than Accelerate， more for devs and ops people。 With lots of examples。For sure， I now understand better the idea of the DevOps revolution。 Very happy to have that。 Also， got some ideas about how to start DevOps in the company I'm working in these days。 Basically， the principles in this book I like the most are: get into the flow， make sure to get faster and useful feedback， and I love the book。 It's a predecessor for Accelerate， from the same authors and the State of DevOps。 To me， more technical than Accelerate， more for devs and ops people。 With lots of examples。For sure， I now understand better the idea of the DevOps revolution。 Very happy to have that。 Also， got some ideas about how to start DevOps in the company I'm working in these days。 Basically， the principles in this book I like the most are: get into the flow， make sure to get faster and useful feedback， and set up and culture of continuous learning and experimentation。 。。。more
Luke
，
This book taught me about the disciplines that make up devops and gave me tons of ideas for how to make any organization pursue fast flow of work， rapid feedback， and organizational growth through learning。 The authors use case studies to bring to life many of the principles of devops。 The case studies are exciting and gave me the feeling of being part of a growing movement。 The book would seriously benefit from a top to bottom edit， though。 First there are tons of grammatical， punctuation， and This book taught me about the disciplines that make up devops and gave me tons of ideas for how to make any organization pursue fast flow of work， rapid feedback， and organizational growth through learning。 The authors use case studies to bring to life many of the principles of devops。 The case studies are exciting and gave me the feeling of being part of a growing movement。 The book would seriously benefit from a top to bottom edit， though。 First there are tons of grammatical， punctuation， and formatting mistakes that drew my attention away from the core materials。 And second you can really tell that different authors wrote different sections of the book。 This incongruity not affect the case studies thankfully。 The publisher should seek to synthesize the book， give it a single voice。 Or not。。。 。。。more
Todd Cheng
，
A high level share on the application of DevOps in the the IT support model。
Monica
，
This was a good read， and a good intro into DevOps。 My main issue was that， like most books of this type， it gives great overviews of the ideas， but was lacking in practical application。
Christoph Kappel
，
That was an awesome read， almost a bit better than "The Phoenix Project"， which this book is basically based on。 The first few pages where a bit weird， especially with all the references to "The Goal"， but it keeps getting better until the end。I really like the writing， with a bit of theory， some real world examples and a conclusion at the end of every chapter。 All technical books should be like that， some are， but should be a general rule。 That was an awesome read， almost a bit better than "The Phoenix Project"， which this book is basically based on。 The first few pages where a bit weird， especially with all the references to "The Goal"， but it keeps getting better until the end。I really like the writing， with a bit of theory， some real world examples and a conclusion at the end of every chapter。 All technical books should be like that， some are， but should be a general rule。 。。。more
Alexej Gerstmaier
，
What an excellent book！ Taught me so much。 Reading The Goal und The Phoenix Project beforehand made it even more interesting
Samuel Bangslund
，
An understandable theoretical approach to the concepts of DevOps， with a lack of practicality needed to realize it。
Puneetsingh
，
When I shifted from being a developer to an SRE it took some time to get used to it but there were still some unclarity in my long term goals。 this book as a lot example on how devops can help transform an org。I gave me perpective on what kinda of place i want to work in and how to make that place happen
Abhi Yerra
，
For running a DevOps company this is the first book on DevOps I've actually read。 Overall， if you have seeped into modern DevOps a lot of this stuff won't be new， but I think if you are a company founder or trying to understand DevOps as a culture for business improvement this should be read。 A lot of the ideas of DevOps are a mix of Lean Startup， Lean Manufacturing， Agile Programing and Theory of Constraint applied to the deployment of software。 For running a DevOps company this is the first book on DevOps I've actually read。 Overall， if you have seeped into modern DevOps a lot of this stuff won't be new， but I think if you are a company founder or trying to understand DevOps as a culture for business improvement this should be read。 A lot of the ideas of DevOps are a mix of Lean Startup， Lean Manufacturing， Agile Programing and Theory of Constraint applied to the deployment of software。 。。。more
Kigenyi
，
Covers a lot more than just Dev and Ops。 It falls more in the management category。 Truly eye-opening。 Though repetitive
Vlad Ardelean
，
Nice book！ Widened my horizons about what kinds of things are necessary/possible to get code really fast into production。Apparently version control for operational things （apache configs， firewalls， deployment scripts。。。non-code things） is quite important！Worth mentioning: Puppetlabs' "state of devops report" and the DORA report are places to check out， surveying the entire industry。The part about how to transform an organisation， by using one devops seed team also made some sense！Worth reading。 Nice book！ Widened my horizons about what kinds of things are necessary/possible to get code really fast into production。Apparently version control for operational things （apache configs， firewalls， deployment scripts。。。non-code things） is quite important！Worth mentioning: Puppetlabs' "state of devops report" and the DORA report are places to check out， surveying the entire industry。The part about how to transform an organisation， by using one devops seed team also made some sense！Worth reading。 I listened to the audiobook， so since it was harder to highlight sections from it， I'll probably remember less than I'd like :） 。。。more
Chris Mann
，