- Paperback: 480 pages
- Publisher: IT Revolution Press (1 December 2016)
- Language: English
- ISBN-10: 1942788002
- ISBN-13: 978-1942788003
- Product Dimensions: 14.8 x 2.7 x 22.9 cm
- Average Customer Review: 8 customer reviews
- Amazon Bestsellers Rank: #43,861 in Books (See Top 100 in Books)
Other Sellers on Amazon
+ 117.15 Delivery charge
The DevOPS Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations Paperback – 1 Dec 2016
Save Extra with 3 offers
- Cashback (2): Get 50% cashback up to Rs. 50 using Axis Bank Credit & Debit Cards. Valid only on your first 2 online payments. Cashback will be credited as Amazon Pay balance within 10 days from purchase. Here's how
- Get 25% back up to Rs. 50 back on your first order using Amazon Pay UPI. Cashback within 10 days. Link Bank Account Here's how
- No Cost EMI: No Cost EMI available on Amazon Pay ICICI credit cards on orders above Rs. 3000 Here's how
- Bank Offer: 5% Instant Discount on ICICI bank Credit and Debit EMI transactions Here's how
Frequently bought together
Customers who bought this item also bought
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.
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.
Jez Humble is Vice-President at Chef. He has worked with a variety of platforms and technologies, consulting for non-profits, telecoms, financial services, and online retail companies. His focus is on helping organizations deliver valuable, high-quality software frequently and reliably through implementing effective engineering practices. He lives in San Francisco, California.
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.
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 mobile phone number.
Customers who viewed this item also viewed
There was a problem filtering reviews right now. Please try again later.
Organizations should aspire to create high performing teams. Instead of culture of fear, have a high trust, collaborative culture. Business value of DevOps is measured by metrics like throughput, code deployment lead time, reliability metrics, mean time to restore (MTTR), organization performance, productivity market share, market capitalization.
The book is divided into five parts.
Part I begins with a brief history of the DevOps movement and introduces the underpinning theory and key themes from relevant bodies of knowledge spanning over a decade. High level principles of the three ways – flow, feedback and continual learning and experimentation are presented. Delivery of work from Dev to Ops to Customers can be accelerated by limiting Work-in-progress and reducing batch sizes. This helps in reducing the number of handoffs. Foster a high-trust culture and a scientific approach to organizational improvement. Risk taking should be part of daily work.
Part II shows how and where to start DevOps journey. It presents concepts such as value streams, organizational design principles and patterns, organizational adoption patterns along with relevant case studies. DevOps is for both greenfield and brownfield products. Start by finding early innovators and adopters, build critical mass and silent majority. Understand the work being done by different value streams and identify teams supporting value streams – Product Owner, Developer, QA, Ops, Infosec, Release Managers, etc. Create a value stream map and a dedicated transformation team by agreeing on shared goals. As a general principle, keep 20% of bandwidth for reducing technical debt. Case studies from LinkedIn and NordStorm demonstrate how dramatic improvements can be made in lead time and quality when problems were identified in value stream and technical debt was systematically paid down. Conway’s Law should be kept in mind while forming teams and architecting products. Every team member should be encouraged to be a generalist and testing, Security checks should be everybody’s job. Embed Ops Engineers into service teams and integrate Ops into Dev rituals.
Part III shows how to accelerate flow by building foundations of our deployment pipeline, enabling fast and effective automated testing, Continuous Integration, Continuous Delivery and architecting for low-risk releases. This Part covers the foundations of deployment pipeline and dev, test & production environments. The stress is on a single repo of truth for the entire system. For a successful CI/CD pipeline it is essential to continuously build, test and integrate. Trunk based development and Continuous Integration are really the building blocks of a successful DevOps practice. The binary deployment should be decoupled from the release cycle. Techniques like Blue-Green deployment can be used to seamlessly deploy on the production environment. The software architecture should also be focused towards productivity, testability and scalability. It should be evaluated whether new paradigm like microservices architecture can be a better fit. There are many ways to migrate from legacy Monolithic architectures to Microservices architecture.
Part IV presents the tools to accelerate and amplify feedback by creating effective production telemetry to see and solve problems, better anticipate problems and achieve goals, enable feedback so that development and operation teams can safely deploy changes, integrate A/B testing into daily work and create review and co-ordination process to increase the quality of our work. Faster feedback loops should be put in place to achieve quality, reliability and safety in value steam. Create centralized telemetry infrastructure for data collection at business logic and storing events & metrics. This will go a long way in troubleshooting problems.
Part V emphasizes the need of continual learning and how we can accelerate it by establishing a just culture, converting local discourses into global improvements and properly reserving time to create organizational learning and improvements. Establish just culture, inject production failures, convert local discoveries into global improvements, reserve time to create organizational improvements and learnings.
Part VI delves into the integration of security and compliance into our daily work by integrating preventive security controls into shared source code repositories and services, integrating security into deployment pipeline, enhancing telemetry to better enable detection and recovery, protecting deployment pipeline and achieving change management objectives.
In summary, DevOps transformation can enable the creation of dynamic learning organization, achieving the amazing outcomes of fast flow and world class reliability and security as well as increased competitiveness and employee satisfaction.