The New Stack today is releasing its third and final ebook in the cloud native technologies series, the Guide to Cloud Native DevOps. This guide helps define a cloud native approach to DevOps and describes some of the modern practices that DevOps teams follow to build, deploy and manage cloud native applications at scale.
Writing this DevOps ebook challenged us. Why write an ebook at all about DevOps? The story has been told quite thoroughly by leagues of experts. For The New Stack, it’s a bit different. We look at the issue in terms of scale. As we explain and analyze what scale means, DevOps practices surface again and again in the research, interviews and data. In developing our Guides to Cloud Native Microservices and Serverless Technologies one major theme emerged: cloud native implementations cannot succeed without mature DevOps practices.
Such practices have been built upon and refined for over a decade in order to meet the deeply complex challenge of managing applications at scale. And DevOps is now undergoing another transformation, buoyed by the increasing automation and transparency allowed through the rise of declarative infrastructure, microservices and serverless architectures. This is cloud native DevOps. Not a tool or a new methodology, but an evolution of the longstanding practices that further align developers and operations teams.
Some of the evolving practices we cover in the Guide to Cloud Native DevOps include:
- Containers, Kubernetes and DevOps
- Finding efficiency through automation.
- Cloud native DevOps roles and responsibilities.
- DevSecOps and DevNetOps.
- A culture of transparency and communication.
- Monitoring, metrics and feedback loops.
Practices have evolved quickly. There is a “new guard” of full-stack developers — in the words of our friends at LaunchDarkly — who all have some part in developing and managing services. Developers now count on approaches that treat the architecture as invisible, allowing them to program the resources according to the workloads their team is managing. Similarly, the operations story is quickly changing as the role of site reliability engineer (SRE) grows and becomes more associated with overall services management.
Roles and responsibilities are changing as infrastructure is abstracted into the cloud and becomes more programmable. A reimagining of the interactions between developers and operations teams is well underway. And as a result, the definition of DevOps changes as well.