I just returned from a week in Las Vegas at AWS re:Invent, Amazon Web Services’ annual conference. I have either attended or watched the live stream every year for the past several years, and I am continually amazed at the number of new services and features that AWS cranks out annually. During the course of each year, I keep reading about how the other public cloud providers are gaining ground on AWS. However, I am not seeing that. Amazon is dominating with large enterprises and Fortune 500 companies. Many of the big wins from the other cloud providers are in companies looking at multicloud strategies or targeting specific workload types (e.g., Google for big data workloads).
Articles Tagged with continuous delivery
Puppet recently published its annual State of DevOps report. Previously, its 2014 report revealed that DevOps was becoming widely accepted in the enterprise. The 2015 report explained that as enterprises become more mature with DevOps, they become higher performing and release software more frequently with better quality. This year’s report has expanded the research to include employee loyalty, security, and lean product management.
I was at the Santa Clara Convention Center, next to the beautiful brand-new San Francisco 49ers stadium, this week to listen to two days of discussions about continuous delivery and Jenkins. Keynote speakers were Kohsuke Kawaguchi, creator of Jenkins and CTO at CloudBees, and Gene Kim, coauthor of The Phoenix Project and well-known speaker on DevOps.
As companies embrace the DevOps movement, they rely heavily on automation to improve the time to market for new features and services. DevOps is a long, never-ending journey with a goal of continuously improving the software delivery process, resulting in better products and services and, ultimately, happier customers. At the beginning of their DevOps journies, many companies focus on continuous integration (CI), in which they automate the build process. Automated testing is implemented so that builds will fail if any changes fail the baseline tests. The idea here is to never move bugs forward, catching them early in the process.
DevOps is gaining serious momentum within enterprises as of late. The big business driver is the pursuit of agility and improved reliability and quality. Adopting DevOps can be challenging because it often requires drastic changes in culture, process, and technology. Those companies that have had success with DevOps often discover some hidden benefits that they may not have anticipated when they started their journey.
If you are like me, you are probably tired of the endless articles talking about DevOps. Each day, you are guaranteed to see an onslaught of articles on the following topics:
- What Is DevOps?
- DevOps Is a Culture Change
- DevOps Requires Empathy
- DevOps Unicorns, or All Unicorns Started Out as Horses
- Buy My DevOps Tools (from many vendors)
- The Wall between Dev and Ops.