Use of Serverless (2017-2018)
Though most DevOps teams are still not using serverless architecture, the technology is definitely rising in popularity, jumping from 30% to 42% from 2017 to 2018.
Use of Container Orchestration (2016-2018)
According to a survey, container orchestration has grown dramatically in the past two years. Way back in 2016, 72% of DevOps Pulse respondents did not practice container orchestration services. Today the number of respondents using Kubernetes has increased tremendously to almost 34%, while Docker Swarm remains a solid alternative at close to 15%.
Open Source Goes Mainstream (2016, 2018)
In 2016, 57% of DevOps teams surveyed had a strong preference for open basis technology. According to the survey, today, 63% responded that half the technology they practice or more is open source, with 61% contributing at least rather open source technology.
In 2016, more than 80% of DevOps Pulse respondents had a CI/CD strategy, were in the development of implementing one, or were considering the opportunity. By 2018, the numbers increased with 91% already in the process or thinking about implementing CI and 85% already in the process or thinking about implementing CD. At this point, about 67% have completely implemented CI, and about 53% have fully implemented CD.
Use Case for Log Analytics (2016-2018)
Troubleshooting and forensics have constantly been the most popular use case for log analytics. Though, more and more DevOps teams are using log analytics for alerting. In addition, security has been a rising logging use case as well.
To conclude, DevOps teams are still struggling to bring security into the combination. The majority of DevOps professionals report that they are not working DevSecOps and that there is a lack of knowledge and tools to help in this area. We believe this will change in the near future. As organizations begin to know the growing influence security has on the application release cycle, as well as on obedience, a larger focus will be placed on adding the ‘sec’ into the ‘dev’ and the ‘ops’. To simplify this, these organizations will be capable to make use of an increasing number of DevSecOps top practices, as well as stated tooling. Automated security, code dependency scanning, risk calculations, and developer exercise are just definite of the methodologies that we assume to see increasingly in a study by the end of 2018.