DevOps: what will be relevant

DevOps is a methodology, not a position. In terms of stakeholders, a DevOps engineer is a person who uses devops tools and methodologies to support incremental software development. DevOps is a business enablement.

What will be relevant

We chose the most popular answers. Let’s take a closer look at new aspects of the direction, which will gain a high level of popularity in the near future.

  • Introduction of AI – will allow to automate routine processes. For example, log analysis, tasks that can be described by the script. There are a large number of products with Ai/ML elements on the market that allow reducing testing costs and errors during software development. Log analysis systems that transform from technology systems into complete ETLs, consumer behavioral analysis systems also require very active use of AI/ML. This leads to a significant increase in the cost of tensor computation specialists and large data processing. In the near future, AI/ML technologies will be actively used only for consulting purposes. Policy systems will not be used because of the significant mistrust of AI/ML systems. So, we will not see AI/ML software written in a productive environment soon.
  • Kubernetes will continue to develop – it will take money to deploy servers (they are needed if there is no Kubernetes). At the moment many people are sure that there is no alternative to Kubernetes, but it is not. The main factor here is the technological fatigue from containerization based on docker. Interesting alternatives are emerging. For example, the use of another containerization technology in REDHAT Linux (Centos, Fedora, Oracle Linux) is podman which within 3 years is likely to reduce the share of Kubernetes usage on the corporate level. Kubernetes is not a silver bullet tool for all presented technology platforms. In the near future we expect to see new services based on alternative specialized processors. Swarm64 (processor for work with Postgresql), PaloAlto (processor for traffic analysis). Alternatives will be offered, but in the near future Kubernetes will remain the implementation leader.
  • Development of cloud ecosystem administration tools. Their own and public (Terraform). In this segment, the number of cloud service providers is growing. And customers are becoming increasingly demanding for continuous integration based on various CI/CD systems, motivating providers to provide extensive API integration opportunities. There is a growing need to deploy different products for end users who are not specialists in the technology stack. These two factors force cloud providers to invest in the development of administrative tools and service scaling. Customers rarely face the challenge of integrating CI/CD when choosing a cloud provider.

There is a downside to this situation. Many open source solution developers are increasingly changing product licensing policies for use in the cloud infrastructure, so it is necessary to pay attention to the licensing policy of products and modules that will be used by cloud service providers.

If there is a lot of free time or a great desire to know Linux in all its details then we highly recommend to use Gentoo in real life, with all the nuances of configuration. But it is time consuming and can develop a hatred for Windows and we have to remember that all these are tools for solving problems and all ecosystems have their own application. Windows often wins in the speed of applications, despite the clutter. So you have to know all these things if you want to use devops methodology.