Originally Published on ToolBox for IT

 

DevOps as a methodology is widely understood and accepted among the IT industry. It was created to integrate all software development and deployment stakeholders and create a single automated workflow that promises a stable and reliable application.

According to GitLab’s Fourth Annual Global DevSecOps Survey, DevOps adoption rates are on the rise, with 25% of companies using it for between three to five years, while 37% of companies have been using it for one to three years.

DevOps relies heavily on automation, which encourages speed, consistency, and reliability. Ultimately, automation in DevOps includes everything optimized from building, deploying, and monitoring.

But as automatic processes and new technologies continue to be implemented, one begins to wonder what the role of the DevOps engineer will look like in the future?

 

Kubernetes and DevOps: Match Made in Heaven?

 

Kubernetes has become the de-facto standard for building distributed apps. When combined with DevOps, it enables organizations to easily deploy apps and services to their customers without having to build complex infrastructure or integrations.

This essential component of a DevOps team’s strategy enables them to automate and scale their applications while mitigating the infrastructure burden and at the same time simplify the deployment of apps by letting them run anywhere.

The Kubernetes platform follows an open-source framework that enables DevOps teams to leverage the latest technology and services without deep vendor-specific skills.

Since different components and technologies exist and deployments happen frequently, it is very hard to manage and deploy applications. This is extremely important when trying to minimize the impact on existing users.

With Kubernetes, developers can easily test their apps in production while also allowing them to stop, redeploy, and restart the container without impacting the service that is being operated.

With the rise of managed services, and the use of the public cloud combined with Kubernetes, the question in many people’s minds is how this automation will change the role of DevOps engineers.

 

Automation is Everywhere

 

The number of cloud solutions has grown significantly over the years, and according to Gartner, the total revenue of cloud service businesses will increase by 40% from 2020 to 2022. Meanwhile, the software as a service (SaaS) market is expected to grow in 2020 to $104.7 billion.

Many of these new solutions include built-in automation. Every year, new IaaS, PaaS, and SaaS products are launched to make the development and maintenance of other applications easy and effortless. Services like JFrog and CircleCI free developers from the burden of dealing with DevOps challenges.

Furthermore, today anyone can build a website with Wix or WordPress, open an online store with Shopify, or use Appy Pie to build an app without knowing how to code, thereby decreasing dependency on developers.

Looking at all these, you may ask yourself – is DevOps a self-destructive profession? Or should an entirely new approach to it be adopted?

 

Is a DevOps Paradigm Shift Required?

 

Although it’s been established that DevOps as a methodology exists, it seems people forget it was originally created to break down silos between development and operations and don’t see that having a separate team in charge of operations and maintenance defeats the purpose.

I believe it’s time to start integrating these two areas.

There will come a time when developers will be required to practice DevOps. Understanding the costs of the application and knowing how to build a more scalable and secure application will ultimately make a better developer.

From a DevOps point of view, understanding the application stack and the team’s pains and needs will help build better CI/CD pipelines, better monitoring solutions, and better cloud architectures.

Actually, according to GitLab’s survey, this change is already taking place. 35% of developers say they define and/or create the infrastructure their app runs on, and 14% actively monitor and respond to that infrastructure – a role traditionally held by operations.

Some companies, like Monday.com, have already acknowledged that it isn’t optimal to have a separate team or a single person in charge of all the operations and maintenance of applications and that it is better to have developers responsible for their application stack from end to end.

It would also be helpful if universities and coding courses would acknowledge these changes and include these subjects and principles in their curriculums.

So, while DevOps isn’t going anywhere anytime soon, a new approach to it should be adopted.