The Future of DevOps

DZone 's Guide to

The Future of DevOps

The future of DevOps will probably see continued growth of the cloud, tools facilitating automation, containers, and company-wide collaboration.

· DevOps Zone ·
Free Resource

To gather insights on the state of the DevOps movement in 2017, we talked to 16 executives from 14 companies who are implementing DevOps in their own organization and/or providing DevOps solutions to other organizations.

Here's what they told us when we asked, "What’s the future for DevOps from your point of view? Where do the greatest opportunities lie?"

Time. There’s a natural clock that you can’t force. There’s a healthy symbiosis between DevOps and the Cloud. As AWS, Red Hat, and Azure grow, DevOps will grow at doubled acceleration.

If you’re building software that runs in the cloud and scales, then you need a NoOps (or Op-less) environment. You still need operations, but with fewer manual tasks and operations. There’s only two percent adoption of DevOps practices around the world – we have a long way to go. Move from early adoption to general adoption. We need to share stories about what we’ve done and how tools can help remove fear and pain with ongoing monitoring.

Moving to the cloud. AWS is providing more tools to facilitate automation and the consolidation of tools so you don’t have to custom build deployments. We'll be using containers to automate flow through the cloud.

The roles containers play will continue to grow in importance. They're still climbing the hyper-curve with early adopters. Others developing containers or microservices strategies can be effective, but not for everything. It’s good at automated deployments, monitoring, and correcting errors. There are tremendous benefits if done well, but not when it's used in poor ways that cause a backlash. Tools and containers are getting better. What comes next? Greater adoption of public cloud usage even by regulated industry. We bring abstract to where we deploy (inside firewalls, cloud, externally). We can migrate what goes where. Pharma can use the same app to deploy inside or outside the firewall depending on the dataset.

We need to get rid of the name DevOps because ultimately it’s about all departments working together – not just developers and operations.

There will be more and better tools. A system like ours should be easy to set up with off-the-shelf tools; we periodically evaluate such tools to see if we can replace parts of our homebrew setup and we continue to find the tools woefully far behind.

Expansion of the principles beyond development and operations. Application delivery doesn’t begin with developers and end with operations. QA, business planning, BPO, and extending into the business provide a better user experience. Integrate third-party and cloud services better to engage with customers. More alignment with business goals the more success you have.

People with enterprise-oriented legacy apps find a way to improve the speed and quality of all apps. Code is constantly being developed. We need to be focused on how we can evolve these enterprise apps to a DevOps methodology.

We'll be optimizing automation faster and with less risk. Technologies are coming out focusing on creating layers of abstraction leading to greater flexibility and portability. Containerizing services and abstracting servers, containers, and nodes will be run on Apache Mesos and Kubernetes. Servers abstract away from servers for better CPU use.

Build an open feedback loop of customer use of the software driven by data from the customer site with machine learning and AI implementing the next feature. Move from Service Oriented Architecture (SOA) to an API architecture. APIs are becoming part of your core business. APIs will be standardized, well-documented, and of high quality.

Apps are more of a part of business and customer experience is driven by apps. Continuous delivery helps make companies more Agile. It will take longer for certain ideas and concepts to be adopted and to learn what works for a particular organization and what doesn’t.

DevOps is becoming everything – development, operations, security, testing, and deployment. We are going to see employees become more versatile – multi-skilled “jacks of all trades” instead of “master of one.” I think this is a good thing since people will be looking at the product from a wider angle and will have a better view of everything when they’re working as a team.

We will continue to see more virtualization, more tools, and more methodologies. The barriers to implementation will begin falling away. With more successes comes greater adoption and understanding. People in the middle will become leaders in implementing the methodology. A great deal of maturation will take place over the next five years.

Everything is in code and version control early on. There will be containerization across the enterprise. Everyone can collaborate in the cloud in containers.

What's the future of DevOps from your perspective?

By the way, here's who we spoke to! 

  1. Michael Schmidt, Senior Director, Automic

  2. Amit Ashbel, Director of Product Marketing and Cyber Security Evangelist, Checkmarx 

  3. Sacha Labourey, CEO and Founder, CloudBees

  4. Samer Fallouh, V.P. Engineering, Dialexa

  5. Andrew Turner, Senior Architect, Dialexa

  6. Andreas Grabner, Technology Strategist, Dynatrace

  7. Anders Wallgren, CTO, Electric Cloud 

  8. Job von der Voort, V.P. of Product, GitLab 

  9. Charles Kendrick, CTO, Isomorphic Software 

  10. Craig Lurey, CTO and Co-Founder, Keeper Security 

  11. Josh Atwell, Developer Advocate, NetApp SolidFire

  12.  Joan Wrabetz, CTO, Quali

  13.  Joe Alfaro, V.P. of Engineering, Sauce Labs 

  14. Nikhil Kaul, Product Marketing Manager Testing, SmartBear Software 

  15. Harsh Upreti, Product Marketing Manager API, SmartBear Software 

  16. Andi Mann, Chief Technology Advocate, Splunk

automation, continuous delivery, devops

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}