Before the Chinese version of this book is published, this article will only reveal to you the general content of this book in advance.
brief introduction
How businesses can increase profitability, improve work culture, and achieve productivity excellence goals through DevOps practices. Today, more than ever, these high-performance management techniques are critical to the business competitiveness of enterprises. For decades, leaders of technology organizations have worked hard to maintain this IT System Agility, Reliability and Security. And then tragic cases still abound -- whether it's the healthcare.gov crash, the breach of cardholder data; or the loss of big data in a cloud computing environment.
However, high-performing businesses that apply DevOps principles (such as Google, Amazon, Facebook, Etsy, and Netflix) can frequently deploy code in production hundreds or thousands of times a day. So how special is DevOps theory, principles, and practice? I believe that everyone will get the answer after reading this book.
In reality, systems are often destroyed, services and products are always unsatisfactory, and the potential of the team cannot be fully realized; development and IT operation and maintenance are opposites, and testing and information security activities are always carried out at the late stage of the project. As a result, even if a problem is found, it is too late to fix; the key activities in product and service delivery often need to be manually operated and handed over to each other, and we always have to wait for other people's work to complete before we can do our own work; the cycle of feature delivery is delayed again and again , quality issues frequently occur, especially those related to deployment in production environments, which in turn have a negative impact on customers and the business.
As a result, not only did our work not get done as expected, but the entire company was dissatisfied with the performance of the IT department, even resulting in budget cuts and IT staff feeling unfulfilled and powerless to change processes and their outcomes. Therefore, we need to change the way we work, and DevOps can guide us.
The goal of this book is to provide the theory, principles, and practices necessary to go from initiating a DevOps transformation to achieving the desired outcomes.
The whole book is divided into 6 parts, using the "three-step work method" proposed in the "Phoenix Project" book to cover the DevOps theory and principles. This book is not only for everyone who works in or affects the technology value stream (usually including product management, development, QA, IT operations, and information security), but also for business and market leaders, most technology initiatives are derived from them.
Our aim is to build on the applied knowledge of the core concepts in each domain, and then use this as a basis to introduce other necessary content to help practitioners work with all colleagues across the entire IT value stream and establish common goals.
This book will be valuable to business leaders and stakeholders who increasingly rely on technology organizations to achieve their goals.
The first part briefly introduces the history of DevOps and introduces the theoretical underpinnings and key themes of the relevant body of knowledge over the decades, followed by an overview of the principles of the "three-step approach": flow, feedback, and continuous learning and experimentation.
The second part describes how and where to start, and introduces concepts such as value streams, organizational design principles and patterns, organizational introduction patterns, and case studies.
Part 3 shows how to accelerate the flow by building the foundations of a deployment pipeline: enabling fast and efficient automated testing, continuous integration, continuous delivery, and architecting for low-risk releases.
Part IV discusses how to find and fix problems by establishing effective production telemetry to accelerate and enhance feedback, better predict problems and achieve goals, get feedback so developers and operations can safely deploy changes, and integrate A /B testing is integrated into our daily work, as well as creating a review and coordination process to improve the quality of our work.
The fifth section describes how to accelerate continuous learning by establishing a culture of impartiality, turning local findings into global improvements, and setting aside a certain amount of time for organizational learning and improvement.
Finally, Part VI will describe how to integrate security into the deployment process by integrating preventive security controls into shared source code repositories and services, enhance telemetry for better detection and recovery, secure deployment pipelines, and implement Change management goals to properly integrate security and compliance into day-to-day work.
By codifying these practices, we hope to accelerate the introduction and application of DevOps practices, increase the success rate of DevOps initiatives, and reduce the energy required to activate DevOps transformation.
original author
4 people
Jene Kim, the lead author of the book, began co-writing it with three other authors after publishing The Phoenix Project. Jez Humble is the author of Continuous Delivery and a key initiator of the practice and concept of Continuous Delivery. Patrick Debios is the initiator of the DevOpsDays conference. He was the first to use the short hashtag #DevOps on Twitter and is an important figure in the DevOps movement and community. John Willis was one of the early movers of the DevOps community and was formerly Director of Ecosystem Development at Docker.
translator
4 people
After I contacted the People's Posts and Telecommunications Publishing House and conducted a trial translation, a translation team was organized. Wang Lei and Ma Bowen are the technical leaders in the DevOps circle that I have met in recent years; Zeng Chaojing is a senior expert in the field of IT management and my former colleague. Wang Lei's works include ["Microservice Architecture and Practice"](https://www.amazon.cn/dp/B018SRCFI6/); Ma Bowen's translated books include ["DevOps Practice"](https://www.amazon .cn/dp/B01LWLRQF3/)
>Liu Zheng, Senior Architect of Nutanix. Exin's first batch of domestic DevOps Master and DevOps Professional certified instructors. Holds Red Hat RHCA certification and AWS Advanced Architect certification. Familiar with IT service management in enterprise data center. Currently committed to promoting DevOps-related concepts and practices, actively participating in training and seminars in the DevOps community, and the core organizer of DevOpsDays in China.
>Wang Lei, former ThoughtWorks chief consultant, EXIN's first domestic DevOps Master certified coach. An early pioneer in advocating and practicing microservices, and author of the first domestic microservice architecture related book "Microservice Architecture and Practice". With more than 10 years of experience in the software industry, he has rich practical experience in service-oriented architecture, continuous delivery and DevOps transformation. At the same time, he is also the co-founder of Xi'an DevOpsMeetup, the organizer of Xi'an GDCR, and has translated "Ruby Gems Development Practice". Book.
> Ma Bowen, former ThoughtWorks senior consultant, AWS assistant architect. He has been engaged in web development and DevOps for many years, familiar with continuous delivery and microservices. Participated in the translation of books such as "Scala Programming Practice" and "DevOps Practice", and was the initiator of the DevOps Meetup event in Xi'an.
>Zeng Chaojing, senior solution consultant of Micro Focus, participated in Exin's first batch of domestic Devops Master instructor certification training. He has been engaged in consulting work in the field of IT operation and maintenance management for a long time, and has provided IT operation and maintenance management planning for many large enterprises in the energy, finance, air transportation, and government industries. Currently dedicated to exploring the practice of Devops concept in enterprise IT department.
The translation team completed the translation and submitted it to the publisher on December 8, 2017.
Catalog early exposure
This book is currently (the publication date of this article) in the editorial stage of the publishing house. It is expected to be officially published around May. Below is the table of contents for this book.
* Preface
* Preface
* Introduction: Looking forward to the new world of DevOps
* The first part of the three-step work method
* Chapter 1 Agile, Continuous Delivery, and the Three-Step Approach
* Chapter 2, the first step, the principle of mobility
* Chapter 3, Step 2, Feedback Principles
* Chapter 4, Step 3, Principles of Continuous Learning and Experimentation
* where the second part starts
*Chapter 5 Choosing the Right Value Stream as an Entry Point
* Chapter 6 Understanding, Visualizing and Applying Value Streams
* Chapter 7 Designs Organizational Structure with Reference to Conway's Law
* Chapter 8 Integrating operations and maintenance into daily development work
* Part 3 Step 1: Technical Practice of Streaming
* Chapter 9 lays the foundation for the deployment pipeline
* Chapter 10 Achieving Fast and Reliable Automated Testing
* Chapter 11 Applying and practicing continuous integration
* Chapter 12 Automated and low-risk releases
* Chapter 13 Architecture to Reduce Release Risk
* Part 4, Step 2: Technical Practice of Feedback
* Chapter 14 Building a telemetry system that finds and solves problems
* Chapter 15 Analyzing telemetry data to better predict failures and achieve goals
* Chapter 16 Applying Feedback for Secure Deployment
* Chapter 17 incorporates hypothesis-driven development and A/B testing into daily work
* Chapter 18 Establishing review and collaboration processes to improve the quality of current work
* Part V, Step 3: Technical Practice of Continuous Learning and Experimentation
* Chapter 19 Integrating learning into everyday work
* Chapter 20 turns local experience into global improvement
* Chapter 21 Reserve time for organizational learning and improvement
* Part VI integrates technical practices for information security, change management and compliance
* Chapter 22 Integrating information security into everyone's daily work
* Chapter 23 Securing the Deployment Pipeline
* Take Action - Summary of DevOps Handbook
* Appendix
* Additional resources
The above table of contents titles are subject to change during the editorial process of the publisher. But its main content can already be seen.
From the press - IT Revolution Press (October 6, 2016)
[IT Revolution Press] (https://itrevolution.com/book/the-devops-handbook/) is the publisher of *DevOps Handbook*, located in Portland, USA. The Simplified Chinese version of this book is titled "A Practical Guide to DevOps", which is the author's major work after the "Phoenix Project". It shows you how to integrate product management, development, quality assurance, IT operations and Information security is integrated to help you improve the competitiveness of your business and win the market; how to replicate the amazing DevOps experience of predecessors.
So is the DevOps Practice Guide right for you? Authors Gene Kim, Jez Humble, Patrick Debois, and John Willis wrote this book for those looking to transform their IT organization; especially for those who want to actually make significant changes through DevOps to increase productivity, profitability and win the market. Covering many aspects of DevOps transformation, this book is an all-encompassing guide from planning to hands-on. It also covers the historical background of DevOps, the principles that underpin DevOps, and dozens of DevOps case studies. It also provides a variety of best practices that can help organizations unite teams to achieve common goals while gaining senior leadership buy-in.
The DevOps Practical Guide delves into the three fundamental principles of DevOps, which we now call the "Three Steps to DevOps Work," Flow, Feedback, Continuous Learning, and Experimentation." It was written after the book "The Phoenix Project", which also gave a general description of the "three-step method", which later developed into an important part of the first part of the book.
As this book unfolds step-by-step the three-step approach to working with DevOps, readers will gain a clear understanding of how high-performing companies use these principles to succeed. Hopefully, any large organization will be able to replicate the success stories these high performers have used to guide themselves through a successful DevOps transformation. The book is detailed in six parts, including:
- Over five years, the 4 co-authors put more than 2,000 hours of work into the book
- 40+ DevOps case studies including Amazon, Etsy, Capital One, Google, Facebook, Intuit, Nationwide Insurance and more
- Wrote more than 400 pages of DevOps practice guides, lessons learned and work instructions.
- Reference and use DevOps related data from over 25,000 data collection points.
The Phoenix Project (in English) has sold 350,000 copies and was in its fifth printing in February 2018. The DevOps Practice Guide begins with the history of DevOps, explaining how it has evolved from decades of interrelated knowledge, and the associated technologies, architectures, and cultural practices that have arisen from it. With these historical foundations laid for the reader, the reader will be able to gain an in-depth understanding of the principles of the three-step work method. Readers will gradually gain a deeper understanding of today's DevOps-related theories and principles. Various specific principles and patterns are presented in the relevant chapters of this book, and how they can be applied in real technology value streams.
We are proud to announce that the DevOps Handbook - A Practical Guide to DevOps has won the 2016 DevOps Book of the Year Award at: [https://devops.com/the-2016-devops-dozen-winners-announced/] (https://devops.com/the-2016-devops-dozen-winners-announced/)
Online bookstore on Amazon Books
The English version of the book is available on Amazon in three formats: Kindle, hard copy, and audiobook. The ranking and evaluation of this book are as follows. The crawl time of the following picture is: 2018-2-25.
* Rank in Information Management Category: 7
* Rank in Process and Infrastructure: 107
* Ranked in management books: 111
85% of readers gave the book a 5-star review. For the latest status of this book on Amazon, [click here. ](https://www.amazon.com/DevOps-Handbook-World-Class-Reliability-Organizations/dp/1942788002/ref=tmm_pap_swatch_0?_encoding=UTF8&qid=&sr=)
The Japanese version of this book was released in Japan in June 2017, [see Amazon Japan for details](http://amzn.asia/2Yqn47O).
How to use this book
In the previous article "DevOps Climbing Guide" , I analyzed and introduced the DevOps case of Nationwide Insurance Company in the US financial industry, [click here for the original text] (https://martinliu.cn/posts/devops-climbing-guide/). This company uses this book as a reference guide in the process of implementing DevOps, and all DevOps teams continuously compare and improve their DevOps practice status through weekly book clubs. The DevOps project implementation guidelines they summarized are shown in the following figure:
The usage scenarios of this graph within Nationwide are as follows:
-
This figure summarizes the experience gained by the DevOps implementation core team in guiding product development teams (or business teams, service teams, and more than 200 such teams) on a sheet of paper for other teams who have ideas for implementing DevOps. refer to.
-
This climbing guide simplifies the education and orientation of other non-DevOps teams.
-
They divide the DevOps implementation into three phases, using the metaphor of Base Camp, North Slope Camp, and Summit.
-
The technical practices in these three stages are all from the DevOps Handbook, through their screening and sorting, and planning in stages based on their own experience.
Coincidentally, this book is also the only designated textbook for the Exin DevOps Professional [DOP] certification exam. After you study this book, if you want to consolidate and test your mastery of this knowledge system, you can take DOP. Certification training and exams; training is a process of answering questions about this set of knowledge. By taking the certification exam, it is possible to fill in an internationally recognized certificate for your professional resume.
Recommended reading:
2018 China DevOpsDays Beijing Station