What's the Future of DevOps?

DZone 's Guide to

What's the Future of DevOps?

Industry executives' visions for the future of DevOps are wide-ranging, with ubiquity and security being popular responses.

· DevOps Zone ·
Free Resource

To gather insights on the state of DevOps, we spoke with 22 executives at 19 companies implementing DevOps for themselves and helping clients to implement a DevOps methodology. We asked, "What’s the future of DevOps from your perspective, where do the greatest opportunities lie?" Here's what they told us:


  • Improving the day-to-day practices. Small companies and small teams can adopt DevOps and perform very well. They will develop patterns with new ways of doing things and will evolve over time. Learn how to do well and integrate testing early in the process. 
  • The next wave of activity will be its application to where most customers are today in legacy enterprises. How to do DevOps in the datacenter to accelerate software and application development. 
  • Able to break the cycle of failure of customer loyalty by providing a phenomenal CX. Once the customer leaves there’s a 60% chance they’re gone forever. You have one opportunity to provide an outstanding CX. It’s important to deliver innovation faster. Able to fine tune how the customer makes changes in CD, continuous testing, and security earlier. Embrace these changes to win. 
  • A lot to be done and there are opportunities with the cloud. Traditional problems like needing a developer because a lot of infrastructure has gone away – we don’t have to build it, or manage it, ourselves. Democratizes small teams to build scalable systems with fewer people and less expertise. 
  • We’re headed there fast. Offer as much as we can out of the box – security, load testing. Reduce cycle time. More automation out of the box.
  • When people stop talking about DevOps we’ll know everyone has adopted the methodology. It’s not an end in itself. Problems don’t go away – security, tracking, testing, code reviews. The reason we do it is to go faster and change directions more quickly to meet customer demand and stay ahead of our competitors.
  • Doing DevOps well requires fostering a culture of communication and openness. It also necessitates empowering teams to find better ways of working. That behavior is a key enabler for finding and fixing problems in a way that leads to continuous improvement of our DevOps processes. Long after DevOps becomes accepted as the standard way of doing stuff, we envision a broader and lasting benefit coming from the culture that we’ve built while embracing DevOps. 
  • Everyone will be doing DevOps in the near future. People needed to be properly trained in the functions, activities, tasks, and responsibilities. Give developers permissions and responsibilities when you hire them.
  • Continue to expand the footprint so that the infrastructure becomes generic and accessible by APIs. Continued growth of more sophisticated APIs.
  • Our greatest opportunities lie in automation. We are constantly striving for 100 percent automation in testing and deployments to our Dev, Staging and Production environments. With continuous deployments, we are constantly improving the process.
  • Simplification around a core set of values. Simplification of toolchains so that it’s more turnkey. A lot of silos and tools will be integrated – CI, CD, integrated testing, unit testing, feature testing – more of a “God Box.” Ultimately simpler implementation.
  • Further decomposition with microservices and serverless. Managing fleets of things. There will be new tools to analyze large fleets of code and microservices.
  • Standardization and consolidation. Able to standardize interfaces of sub-libraries with regards to CPUs and performance bottlenecks.
  • DevOps will be fully adopted along with the strategy, tools, processes, and culture needed to create value for the consumer, which in turn will create value for the company and their shareholders.


  • Containers become more popular and there is more container technology with overlays across network hosts. The rate of code changes and deployments will continue to increase. Security and DevSecOps will continue to grow. Growth in the security space will be massive. 
  • Improving the security of all code and applications.
  • Database and security should have the same policies in production that are enforced in development. Seeing DevOps algorithms in other groups. It will move more companies to the cloud more quickly.


  • The most exciting is AI/ML in different fields and tools. As tools start to adopt AI, they will find patterns in logs and event monitoring to identify outliers to prevent and solve problems. Work more toward prevention.
  • Self-healing. More tests in place the less the team has to worry. Autoscaling. Close off issues before they occur by being proactive.

Here’s who we talked to:

  • Gil Sever, CEO, Applitools
  • Mike Tria, Head of Infrastructure, Atlassian
  • John Trembley, CMO and Scott Harvey, V.P. Engineering, Atmosera
  • Aruna Ravichandran, VP DevOps Products and Solutions Marketing, CA Technologies
  • Flint Brenton, CEO, Collabnet
  • Tom Hearn, Data Center Architect, Datalink
  • Shehan Akmeemana, CTO, Data Dynamics
  • Robert Reeves, Co-founder and CTO, Datical
  • Anders Wallgren, CTO, Electric Cloud
  • Job van der Voort, Vice President of Product, GitLab
  • Ben Slater, Chief Product Officer, Instaclustr
  • Ilya Pupko, Chief Architect, Jitterbit
  • Tom Joyce, CEO, Pensa
  • Stephanos Bacon, Chief of Product, Portfolio Strategy for Application Platforms, Red Hat
  • Michael Mazyar, CTO, Samanage
  • Eric Wahl, IT Director and John Joseph, Vice President of Marketing, Scribe Software
  • Manish Gupta, CEO and Founder, ShiftLeft
  • Martin Loewinger, Director of SaaS Operations and Jonathan Parrilla, DevOps Engineer, SmartBear
  • Chris McFadden, V.P. Engineering and Operations, SparkPost
automation, cloud, devops, security

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}