DevOps

What will be the top DevOps trends in 2018?

We asked Sergey Sverchkov, Godel’s Head of DevOps, some key questions on what will shift within DevOps this year, and this is what he had to say.

Q: Will we start to see more developer-led initiatives in large enterprises?

Given all the benefits and savings that can be achieved with DevOps practices, I would say that initiatives to change the culture of work with infrastructure, integration, and deployment processes may come from engineering teams, but like any major changes in large-scale enterprises they need the support of top management. These are organisational and process changes that need to be driven by the company and team leads – so must be led by both.

Q: Is DevOps thinking mainstream now? Who’s lagging behind?

It seems DevOps practices are really becoming mainstream, at least in the media! If your ops and dev teams are on the opposite sides of the fence, you are probably lagging behind – and realignment is needed.

Q: Applying successful DevOps strategies: what are the models that organisations could or should emulate?

DevOps practices are designed to make organisations more efficient. They are based on years of experience and best practices accumulated by the industry. So most models are at least worth trying. Whether a certain model or tool will work in your organization depends on the particular use case and applicable legal constraints. For example, storing app data in public clouds might be off-limits for healthcare organisations for example or some great open-source solutions may lack certain certifications, etc. But of course DevOps practices can be applied to organisations with legal restrictions. For example, one can have a private cloud to host all the sensitive data. Also, public cloud providers, like Azure and AWS are constantly working on obtaining industry certifications for their services, e.g., PCI DSS and HIPAA.

Q: What’s the next bundle of letters after DevSecOps?

I’m not sure we know the answer to this one at the moment. Security should be considered at any stage of solution development and it means it is an integral part of DevOps work.

Q: Will DevOps adoption really begin to really kill off traditional ops teams?

I believe the practice is relieving ops professionals from routine work, making them more efficient, reducing the chances of human error, security breaches, as well as their impact on business.. This also means all changes are tracked and we always have a detailed description of the overall IT landscape in the company. Putting ops engineers on dev teams from day one helps to make software more reliable, resilient, scalable, and most importantly, to store infrastructure and deployment processes definitions as code in version control systems.

Q: How is the increasingly mixed container market going to affect it all?

Healthy competition is good for end users, but too many container standards could slow down adoption due to compatibility issues. It will be a balancing act.

Q: From a strategic perspective, will organisations start to look at DevOps vendors like they do VMs or cloud?

Not sure I know the answer. Cloud providers seem to be in a race to add more DevOps tools to their cloud marketplaces. The overall trend among DevOps solutions seems to be maximising portability between clouds. For example, Hashicorp Terraform has providers for many cloud and virtualisation platforms.

Q: What are the benefits of open source for DevOps teams?

Open source is not just from indie developers and startups:

• Open code can be easily inspected by your own engineers, as well as authorities, which may be required for some industry certifications.
• Open source products are generally free to use and modify, so you can’t really beat the price.
• The open nature of OSS means that your organisation could influence how a project is developed, which features get added first, etc.