10 DevOps Trends and Impact for 2018

10 DevOps Trends and Impact for 2018

There is plenty to read on the web about what to expect this year with regard to DevOps and that is because 2017 witnessed more industries adopting a DevOps practice. According to a Capgemini report, 60% of companies have adopted DevOps or plan to do so in 2018. This shows how widely accepted it is becoming to have DevOps be a necessary part of your business strategy.

If you intend to quickly respond to market demands, keep your software and solutions regularly updated, and improve time-to-market, you had better be investing in DevOps practices or start soon.

As DevOps continues to grow, here’s what we expect to see in the upcoming year.

10 DevOps Trends and Impact for 2018

1. 2017 saw great growth in SMB adoption of DevOps and 2018 is expected to be the year for Enterprise adoptions.

In 2017, the number of enterprises to have adopted some aspect of DevOps principles reached 84% according to a study by cloud-management provider RightScale. However, that does not mean these enterprises put DevOps into action in 2017. There is a difference between accepting principles and putting them into action. The same study showed that just 30% of enterprises adopted DevOps company-wide. So while DevOps adoption has gone wide, it hasn’t necessarily gone deep. Experts believe 2018 will be the year when large organizations start not just doing DevOps, but doing DevOps at scale.

2. DevSecOps – 2018 will see Security teams, tools and practices being part of the mix in the early stages of development. 

Getting security involved in DevOps will make businesses more inclusive and will mean security departments will no longer be included at the end of the development cycle but rather, at the beginning. 

3. Monitoring will become new testing as it is not possible or practical to test all conceivable scenarios.

It is said that at scale it just is not possible or practical to test all conceivable scenarios at the end of the product cycle. Instead, DevOps teams will find it more valuable to monitor for live issues and correct them in short cycles. As testing requires you to think of certain problems to look out for, it limits what you may find. By contrast, monitoring will bring up issues as they happen. The adoption of monitoring will allow companies to understand how their software runs in real situations, providing immediate information about their systems. This is invaluable information that needs to be acted upon and used to improve software.  

4. Kubernetes is touted to become the standard for cluster computing, and make Platform as a Service (PaaS) possible.

More companies will join the Kubernetes Open Source Project and provide services on top of their operating systems. Additionally, extensions will be made available by cloud providers and software companies, making it easier to run applications in the cloud. Many of the major cloud providers including Microsoft Azure, AWS and Alibaba are starting to offer Kubernetes as a service, even a “serverless” Kubernetes where nodes are managed by the cloud provider, creating another level of abstraction and simplicity for developers. This brings the majority of the work needed to run a Kubernetes cluster back to these major providers. Because of this, it is expected that there will be more integration between such providers with external tools. This means there is likely to be a shift to focus more on application layers and the services that run off of Kubernetes. This general advancement within Kubernetes will allow easier adoption of advanced monitoring, logging and metric studying within companies. 

5. Serverless technology will take off, accelerating the death of (server) operating systems as we know them.

Operating systems, as we know them, are predicted to disappear and be replaced by operating systems which possess the function to run containers in a Kubernetes cluster. On top of this, operating systems for hosts will suffer from containers as services because in these new environments they will no longer have a host. 

6. The Site Reliable Engineer (SRE) role will be grow in importance.

The more DevOps is adopted the more we’ll see the DNA of IT Ops evolve. This is leading to the mainstream acceptance of a new breed of IT operations professional, the Site Reliable Engineer. The SRE will need to be as comfortable with Python and Ruby as with configuration and capacity, said Rick Fitz, senior vice president of IT markets for Splunk in an interview with TechBeacon.

7. New KPI Metrics will balance Speed with Stability.

The DevOps engine runs on the fuel of measurement. The right blend of metrics gives organizations the visibility to understand what’s working with tools and processes now and what needs to be tweaked or rethought entirely. While there isn’t one perfect key performance indicator – naturally – the best KPI’s will balance Speed with Stability and the best organizations will learn these are not a trade-off. They can and will find the right balance, the right mix for their own organization.

8. A Focus on meeting and exceeding the Business’ Goals will drive ultimate success.

This probably needs no further explanation. It’s that obvious. But it’s worth stating because it is far too easy to get so ‘in the weeds’ as to forget the business goal(s).

9. DevOps will embolden experimentation and therefore innovation.

Good DevOps collects and tracks metrics allowing the organization to do things they’ve never done before and set risk parameters around those experiments so that, when they fail, the impact is limited. This is crucial for innovation. For without permission to experiment and fail, you will never experiment and succeed.

10. Businesses will begin to incorporate DevOps into their IoT offerings.

Increasingly, hardware manufacturers working on IoT devices will see software as an integral part of their product. This involves incorporating DevOps into their business model, making it necessary to have people continuously working on both hardware and software designs. Tesla has jumped on this, and not only develops cars, but also the accompanying software within its vehicles. Software in cars is nothing new, but Tesla has taken it to a whole new level, even delivering updates wirelessly to its cars, over the air. Because of this, Tesla is able to continuously improve and update their products. Using this model allows constant product updates – including safety updates and what would have been a recall, in the past – and still is a recall for the legacy automotive manufacturers. Tesla can respond to user needs at a faster rate. This represents a turning point within the IoT industry, enabling better products and improved communication between multiples devices. Currently in IoT, there is no room for companies to forget about their products once they have been sold. Nowadays, user demand means regular updates for device functionality are mandatory. Companies are going to be forced to acknowledge this – and do it, in order to succeed and turn a stable profit from their IoT devices, as well as please their end users. 


The future of DevOps, what to expect for 2018

8 DevOps trends to watch in 2018

10 top DevOps barriers and trends forecasted for 2018

Other DevOps Articles

DevOps Statistics for 2017 – DevOps Drives Big Changes

What is DevOps?

Get Your Team DevOps Trained and Certified (certification optional)

Choose public or private training. We do both. Public Enrollment Savings: You can enjoy early bird savings in our public classes if you book at least 30 days in advance! Private and/or customized and private delivery is available. We do it all the time! 


MAX DevOps Public Enrollment Class Schedule


Leave a comment

Your email address will not be published.

Loading ...