The crystal ball of DevOps?
In my line of work, predictions on the future of “DevOps Engineering” are discussed quite regularly. According to IDC, the DevOps software market will grow from $2.9 billion in sales (2017) to a $6.6 billion industry in just five years, so it’s no surprise that everyone is trying to work out what the future looks like so they can get ahead of the curve.
This first prediction may come as a bit of a surprise, but in the real world, departments and development tools still remain stubbornly walled off from each other, either for budget reasons or because of dated corporate culture. The goal of eliminating silos remains unfulfilled for now, but our second trend offers hope to the hopeless.
2. Executives Buy-in Will Continue To Rise
Business leaders are burdened with (sometimes) conflicting priorities. Saying yes to one urgent thing typically means saying no to something just as important. For many years, “DevOps” found itself on the losing side of that game. However, Gartner’s analytics survey on “CEO priorities” points to a meaningful shift in their thinking. Growth remains the number one concern of most leaders. However, an increased openness to technology as a means of achieving that growth is on the rise. That being said, 61% of respondents plan to increase their IT spending in 2018.
3. Kubernetes Will Takeover Containerization
With the growth of DevOps comes a growth in the size and complexity of container production clusters. An orchestration tool is needed to deploy and manage container clusters, and Kubernetes has emerged as the orchestration tool of choice. As a demonstration of Kubernetes’ dominance, Docker is now distributing and supporting the tool while still investing in its own orchestration system, Swarm. If a new tool comes along to challenge Kubernetes, we predict it won’t be anytime soon.
4. Security Will Become The Priority
DevOps is rightly praised for prioritizing functional testing earlier in the development process. “Shifting left” has allowed bugs to be spotted and fixed sooner, which in turn has enabled safer/faster production. But early iterations of DevOps delayed considerations around security. This was clearly amiss, as can be seen from the endless reports of data breaches around the world. As DevOps continues its growth, it will transition closer to “DevSecOps” in its approaches. In other words, mainstream DevOps will start treating security as code, making it the entire team’s responsibility from the beginning of the development lifecycle.
What I’ve learned…
As a non-technical person, focusing on recruitment solutions within the world of DevOps, I’ve spent countless nights discussing things like the technical benefits of transitioning from Ansible to Salt Stack or why an organization would prefer to use Chef as opposed to Puppet. It’s even inspired to take on Python development courses, just for sh*ts and giggles.
The tremendous growth within technology has created a shift in the way we work with each other and build things. DevOps “represents a way of thinking that can help enterprise thrive at a time when speed to market means the difference between success and failure.” That being said, more changes are yet to come. All in all, keep your ears to the pipelines and #staywoke.