The DevOps Handbook for Unicorns and Horses
Release Date: 02/23/2017
Our guest on the podcast this week is Ben Bernstein, CEO and Co-founder of Twistlock. We discuss the myths surrounding the security of applications in containers in the cloud and advice for people just starting a container initiative.info_outline Adopting Cloud and DevOps Across 2,000+ Developers at Vanguard
Our guest on the podcast this week is Jeff Dowds, CTO Vanguard. We discuss why Vanguard went to the public cloud, the value of DevOps and best practices for IT leaders who are just getting started on their cloud initiative.info_outline Multi-Cloud vs Hybrid Cloud: What’s the Difference?
Our guest on the podcast this week is , Co-Founder & CEO at We discuss the difference between hybrid cloud and multi-cloud. Hybrid is anything that’s not just one cloud provider, which includes multi-cloud. Multi-cloud is a strategy where some workloads are running on one cloud, some on another. One trend we see is that big enterprises are splitting workloads more and more between at least two major public clouds for a multi-cloud strategy. According to Gartner, 70% of enterprises will be implementing a multi-cloud strategy by 2019. Some do it because they are mandated by...info_outline Edge Computing and how it Transforms Enterprises
Our guest on the podcast this week is , President and COO at We discuss the many definitions floating around for . Some call it fog computing or MEC (mobile edge computing). It is simple. It is a perspective that as the shift goes from wireless networks and person-to-person interaction to machine-to-machine interaction, underlying architectures must change along with that shift. For things like IoT and distributed data, they require reliability and speed at the source. Increased embeddedness from IoT to healthcare, finance to automotives requires lower latency and need...info_outline Kubernetes Wins at Orchestration Engines, but Still Needs Backup
Our guest on the podcast this week is , Co-Founder and VP, Sales at We discuss how Kubernetes has won the war as a leader in orchestration. However, it is still not easy to use or maintain. We explore what organizations need to consider to build operational efficiencies around the technology. Kubernetes, Docker, and containers are very different from something like VMware and Amazon in terms of adoption. When new technology comes into an organization, they usually would quickly become an IT-led project. With containers, they are more like Puppet, Chef, and Ansible. They pop up...info_outline Kubernetes in Enterprises of all Sizes
Our guest on the podcast this week is , Director of Product Strategy at Brian discusses a small bank in Ohio and how they have a business use-case for Kubernetes. Because Kubernetes was built to manage Google-sized technology, it is surprising that there is a reason to apply it to a small brick and mortar bank just starting with web and mobile. What they noticed in the switch is that because customers get paid on Fridays and are more likely to check if they got paid on their personal mobile device, as soon as they launched mobile their Friday traffic soared. For just one fifth of...info_outline RightScale’s 2017 State of the Cloud
We discuss RightScale’s report analyzing trends in the cloud. RightScale helps customers adopt cloud by helping them with a cloud management and optimization. This is the sixth year of the report so we can start to see trends over time now and there were a few interesting takeaways this year. In the report, RightScale asks two big questions for enterprises. First is about cloud strategy and what their intention is on cloud – to use private, public, or combinations of those. Second, they are asked about what they use today for private or public clouds. From a strategy point of view,...info_outline The DevOps Handbook for Unicorns and Horses
Our guest on the podcast this week is , DevOps expert and author at and We discuss “The DevOps Handbook”, which was started over five and a half years ago and released in October 2016. Gene co-wrote the book with Jez Humble, Patrick Debois, and John Willis. The book includes over 48 case studies that range from unicorns like Google, Amazon, Facebook, but also horses like Nordstrom, Target, and Capital One. Many of the case studies came from the . The book has discussions of both greenfield and brownfield deployments, even touching on mainframes. The most common question enterprises ask...info_outline Security and DevOps are Never 100% Done
Our guest on the podcast this week is , Chief Strategic Architect at We discuss Docker adoption, DevOps, and security for a company as big as ADP with over 630,000 customers, 35 million users in 100 countries, and 55 million stored social security numbers. We see how DevOps processes and security is never a completed initiative and can always be improved. We also see how DevOps at ADP varies significantly across projects and seems to mold to the team using it.info_outline Hybrid Cloud is Not a Choice, It’s a Realization
Our guest on the podcast this week is , Founder and CEO at We discuss the differences between Docker Swarm and Kubernetes as well as the debate about how many companies use containers the right way. We also look at hybrid and how it can be easy to lift a container from Amazon and move it to Google, but there will still be key differences in networking and storage between the two that make the shift more complex. Last, we talk about the pros and cons of going all in on one vendor.info_outline
We discuss “The DevOps Handbook”, which was started over five and a half years ago and released in October 2016. Gene co-wrote the book with Jez Humble, Patrick Debois, and John Willis. The book includes over 48 case studies that range from unicorns like Google, Amazon, Facebook, but also horses like Nordstrom, Target, and Capital One. Many of the case studies came from the DevOps Enterprise Summit. The book has discussions of both greenfield and brownfield deployments, even touching on mainframes.
The most common question enterprises ask about DevOps is: Where do we start? “The DevOps Handbook” starts with a chapter on starting with DevOps by picking the right value stream. The research started by looking at where successful unicorns and horses started with their DevOps initiatives.
They also look at the failed DevOps initiatives to learn what to avoid. Failures can be categorized in two ways: starting too small or starting too big. Initiatives that start too small often start with a simple Chef or Puppet project end up looking like like more of a hobby. When they finish the project, they haven’t actually proven anything and the project gets easily dismissed. Initiatives that start too large often choose something too critical to the operations of the organization, and is unforgiving of mistakes. The most successful journeys start with something that creates a material contribution to the organization, but is small enough that it does not get shut down early for small mistakes. Their studies found that one out of three leaders who were starting these transformations were being promoted for their contributions.
There is no one answer for how to change an organization’s culture for DevOps, but there is a prescriptive set of guidelines. The technical practices do not change such as version control, continuous testing, continuous integration, automated deployments, proactive monitoring of the production environment, security integrated into every step. What is different is where these initiatives start from. Some come from the Director ofr Operations, a Chief Architect, or even Director of Development. This transformation starts from different people and teams at different organizations. There are many different ways to reach a great DevOps practice.
The three guiding principles of DevOps are:
- Flow : Maximizing the flow of work and minimizing the lead-time
- Feedback: Creating check-ins and the equivalent of being able to stop the assembly line
- Culture: Fostering a culture of continuous experimentation and learning
There is a myth that with DevOps you can’t have any central control. We discuss differences in self-service teams like Netflix and Amazon to function-based teams used at Google and Disney. We look at Etsy’s liason model assigning ops engineers to various service and product teams.
Many companies do well with the technical aspects of DevOps, but struggle with the culture changes it requires. Ten years from now, it will be about creating learning organizations and the command and control model will not be effective. It won’t be about who caused a problem or who to blame, but will be about creating a culture of learning for a successful team.