How DevOps Has Changed
How DevOps Has Changed
Things changing in DevOps include the level of acceptance, predominance of the public cloud, and tools offered.
Join the DZone community and get the full member experience.Join For Free
To understand the current and future state of DevOps, we spoke to 40 IT executives from 37 organizations. We asked them, "How has DevOps changed since you began using the methodology?" Here’s what they said:
- Most notable is greater awareness. Instead of how different from Jenkins now aware of other tools, understand where and where the different tools in the system apply. Fluency and understanding has improved dramatically. People are understanding the importance of including the database in the process. Maturity as people figured out to get business requirements, write app code and move faster. Realize there’s more to the story of full-stack DevOps. The entire stack needs to be automated in order to be successful in speed and quality.
- More acceptance as people are aware of the benefits and more availability of tooling and knowledge. AWS has added a lot of services over time. People are building tools and products with increased adoption of DevOps – more easily available and easier to adopt.
- Still in infancy. Start-up SMB is using DevOps. Global 2000 is very spotty because ITIL processes are ingrained. Congealing around super developer and getting rid of ops isn’t going to happen, more clarity about the agility of application teams and enablement. Formally a buzzword, now clients looking at adopting DevOps.
- A big change in the past year with maturity of tools, platforms, and thinking. People are embracing and implementing. People understand the benefits. Large organizations are embracing DevOps and new ways of thinking. May lag with legacy systems but seeing a desire to bring legacy processes into DevOps.
- Four to five years ago DevOps was a mythical thing from Silicon Valley with Netflix, Facebook, and Google. Over the last few years more companies getting on stage and talking about how they’ve transformed from within the organization and individuals taking on more responsibilities and automating more. How to share more openly with others. Measurement and sharing is growing. Finance and telco organizations have their innovation labs to attract new people with a different mindset to change the way and the behavior of the traditional employees. Teams are figuring out how the company goes through digital transformation and how to build software and fit within the current organization and processes. They teach the rest of the organization how to do things differently for the future.
- Broader adoption. Infrastructure as code is getting more attention. Culture adoption was the first wave and is now a constant. Now rolling into more tools with software and virtual hardware with infrastructure as code automation. Using automation in CI/CD for fresh environments and blue-green releases.
- Better understanding. Through conferences, articles, podcast the market is much more well informed about what you can accomplish though there may be some differences in understanding what every aspect means. People accept the concepts and want to know how to implement.
Containers and Kubernetes
- It’s a philosophy or thought process but a tactic alignment of DevOps and containers. It’s much easier to do virtualization of code and automation containers make it easier for developers to do work in an environment that looks like production. Containers enable a shift-left attitude. Dev community is hangry for K8s – it’s the standard for automation. K8s is the baseline and developers are jumping on the platform which is much more agile.
- Seen increased adoption. Also, see people coalescing around K8s for managing containers. Containerization is an evolution we’ve seen, and it creates a mindset where I have a configuration that I apply to my test environment and then apply to my production environment. Now build container in non-production and then move to production. VMs and containers, not or.
- At the start, DevOps was primarily used as an operational philosophy. This philosophy was mostly associated with the Agile methodology for development and integrating development and operations functions within the same teams and queues. Treating infrastructure as code grew out of this. With the advent of cloud architectures -- and now containers -- it has become the default way that modern organizations approach working with infrastructure. Now DevOps is less focused on the basic requirements around infrastructure as code and more focused on how to use these concepts to provide continuous integration and delivery pipelines and ensure auditable automation is a component of every function of product delivery. This allows DevOps teams to assist with organizational cost optimization and compliance goals.
- Containerization has been a big change. We've also almost moved from Puppet to Kubernetes!
- We're an early adopter of DevOps enabling the fast scaling of the business. Make sure tools, processes, and standard operating procedures are well understood. We support seeing operation metrics out of the box. Handle logistics of data movement and staying resilient across data centers.
- Since we began using DevOps, the biggest change has been the explosion of tools and infrastructure options in the market for automating the entire DevOps process. Years ago, DevOps was merely a concept of bridging communications and processes between Dev and Ops. Today, DevOps is seen more as a continuous pipeline from planning to production. To optimize the pipeline, and automate all steps in the process, a massive proliferation of tools has emerged. For deployments, it was first Puppet/Chef/Ansible and now Docker is taking over. Everything is done in the cloud. Local labs (physical and even Virtual) are a thing of the past. Cloud/SaaS has been a huge enabler of optimized DevOps pipelines.
- Partly greater mature adoption. How to CD software, eliminate friction, collaboration. Getting faster. The application was not changing. Seeing more non-deterministic applications. The application may change based on the data from sensors. How to test and address that sort of change. Infrastructure applying DevOps focus on CD apply AI/ML for testing and determining patterns. Can put inert features until feedback is provided. Analyze the data. Shifting from deterministic to non-deterministic application DevOps becoming more intertwined.
- Since we began, automation has become the way to do most of DevOps. Many manual processes like testing, configuration and deployment have become automated with various tools. Also, with the advent of the cloud, DevOps automation has become cloud-centric now.
Here's who shared their insights with us:
- Tim Curless, Senior Technical Architect, AHEAD
- Will Hurley, Vice President of Software Lifecycle Services, Astadia
- Lei Zhang, Head of Developer Experience (DevX), Bloomberg
- Ashok Reddy, Group General Manager, CA Technology
- Sacha Labourey, CEO, CloudBees
- Logan Daigle, Director DevOps Strategy and Delivery, CollabNet
- Sanjay Challa, Senior Product Marketing Manager, Datical
- Colin Britton, CSO, Devo
- OJ Ngo, CTO, DH2i
- Andreas Grabner, DevOps Activist, Dynatrace
- Anders Wallgren, CTO, Electric Cloud
- Armon Dadgar, founder and co-CTO, HashiCorp
- Tamar Eilam, IBM Fellow, Next Generation Cloud and DevOps, IBM Research
- Mathivanan Venkatachalam, Vice President, ManageEngine
- Jim Scott, V.P., Enterprise Architecture, MapR
- Mark Levy, Director of Strategy, Micro Focus
- Glenn Grant, President - U.S. East, Mission
- Jonathan Lewis, VP of Product Marketing, NS1
- Zeev Avidan, Chief Product Officer, OpenLegacy
- Tyler Duzan, Product Manager, Percona
- Bradbury Hart, Vice President and Chief Evangelist, Perfecto
- Damien Tournoud, Founder and CTO, Platform.sh
- Bob Davis, Chief Marketing Officer and Jeff Keyes, Director of Product Marketing, Plutora
- Brad Micklea, Senior Director and Lead, Developer Business Unit, and Burr Sutter, Director, Developer Experience, Red Hat
- Dave Nielsen, Head of Ecosystem Programs, Redis Labs
- Brad Adelberg, Vice President of Engineering, Sauce Labs
- Adam Casella, Co-founder and Glenn Sullivan, Co-founder, SnapRoute
- Dave Blakey, CEO, Snapt
- Keith Kuchler, Vice President of Engineering, SolarWinds
- Justin Rodenbostel, Vice President of Open Source Applications, SPR
- Jennifer Kotzen, Senior Product Marketing Manager, SUSE
- Oded Moshe, VP of Products, SysAid
- Loris Degioanni, CTO and Founder, Sysdig
- Jeffrey Froman, Director of DevOps and Aaron Jennings, Engineer, Temboo
- Pan Chhum, Infrastructure Engineer, Threat Stack
- John Morello, CTO, Twistlock
- Madhup Mishra, Vice President of Product Marketing, VoltDB
- Joseph Feiman, Chief Strategy Officer, WhiteHat Security
- Andreas Prins, Vice President of Product Development, XebiaLabs
Opinions expressed by DZone contributors are their own.