DevOps adoption started nearly 8 years ago and the movement is quite widespread by 2018. However, many fledgling startups and full-scale enterprises alike are still afraid of transition to DevOps. This is due to the way both startup entrepreneurs and enterprise C-suite managers think. Their main idea is often: “If it works — it isn’t necessary to pay attention/money to improve it”. This way the enterprises continue to stick to the old and trusted ways, like having their mission-critical systems running on the servers inside their buildings and splitting the tasks, skills, and tools between the Development, the QA and the Operations departments. For startups, it means favoring the continuity of services availability and user experience over the frequency of new features implementation. It should be done to avoid risk and ensure stable product performance, minimizing the possibility of service downtime. State of DevOps adoption: the results are great, yet there is much to do DevOps approach to software delivery can answer all of these challenges and provide multiple benefits, according to the survey results from the latest from Puppet. 2017 State of DevOps report Here are some of the most interesting insights and outcomes of that report: Companies that adopted the DevOps methodology boast , meaning the next batch of code can be delivered to the production environment in mere hours, not in weeks. 46x more frequent code deployment The choice to follow the DevOps principles of IaC, CI and CD ensures , so that the code is built, tested and deployed to production in less than an hour. The result is frequent deployments described above. 440x shorter time from committing to release Many businesses fear that frequent deployments might lead to less diligent testing and critical failures in the code, which will cause serious service interruptions and will reduce user’s impressions.Quite the contrary, having an automated testing pipeline for in-depth code testing and immutable versioned infrastructure prevents or minimizes that. This actually leads to (time to recover) if any failures occur, not to mention these (only around of code pushes now lead to issues, instead of (on average) the companies faced before their transition to DevOps, according to ) 96x faster TTR failures occur 5x less frequently 7% 35% Puppet When DevOps transformation has wholehearted support from the C-suite through all the managers and down to the grassroots, the initiative brings fruit . More than of respondents stated implementing the in their organizations helped achieve all the goals set. However, about of the respondents said the lack of a charismatic and inspirational leader has lead to the DevOps initiatives stalling and failing. 2x faster 65% DevOps culture 50% Nearly of the businesses have already accomplished the DevOps implementation or are currently undergoing the process, with more percent of respondents stating this as a priority task for the next few years. 27% 41% Automation accounts for a great deal of DevOps services as it allows streamlining quite a chunk of routine tasks, freeing up the resources for creative and innovative efforts. For example, automating the code delivery can save:– around of resources and time devoted to due to building automated unit tests using the tools like ;– at least of resources and time devoted to due to ;– more than of the to avoid unnecessary bottlenecks and managerial overhead;– about of resources and time devoted to due to using the solutions like or , Ansible, Salt, Chef or Puppet. 27% testing Codeception 30% code deployment building automated deployment pipelines with GCP and Kubernetes 27% approval and workflow processes 33% configuration management Kubernetes container management tool Terraform configuration orchestration platform Tools can be great, but DevOps culture is paramount As Atlassian (the leading provider of collaboration software) stated in their , of IT experts are familiar with DevOps-as-a-service to some extent, while are still not aware of its benefits. Thus said, this of companies have quite a huge advantage over their competition… DevOps adoption report 41% 59% 41% that responded to Atlassian survey have experienced the positive results of DevOps transition already. Nevertheless, of these specialists stated the increased strain of their evolved responsibilities might lead to burnout. 90% of IT specialists 70% Why so? Because removing the silos of tasks and teaching the members of Dev and Ops departments to use each other’s tools is not actually the way to build an efficient DevOps workflow in an organization. The aforementioned report mentions several important issues: of respondents state there are only and cross-learning practices within the newly-formed DevOps teams. When the need to share some knowledge does arise, it is usually provided in a static form of documents, not in interactive chats, groups or wikis. Merely of respondents pride themselves on having , as well as the eagerness to collaborate and solve the issues. 80% limited knowledge sharing 17% open access to all the required information While every business deploys some , only of respondents reported having systems in place. This means that only ⅔ of the companies can mitigate the negative events quickly enough and remove the root causes of the issues, instead of dealing with the consequences like the customer’s frustration due to the service unavailability. , you know. monitoring and logging tools 64% proactive monitoring and smart alerting An ounce of cure is worth a gallon of treatment Almost all respondents stated their companies have automated the testing or were in the process of implementing automated continuous delivery pipeline. Nevertheless, nearly said after pushing the code to production. This means CI/CD initiatives have not yet matured well enough and the new code is not tested with the rigor and workload of the real production environment. 42% they still needed manual hotfixing of minor bugs Disaster management is still far from perfect, as nearly of respondents had to admit their for different type of incidents that occur. Thus said, half of the DevOps engineers still rely on manual firefighting and awaits directions from the managers, rather than following a clearly-defined guideline. 50% approaches, processes, and responses vary A brief summary of AWS and Azure DevOps-related stats Sumologic has published an end-of-the-year . report on the state of affairs in the cloud in 2017 The report was comprised of the answers of more than 1500 Sumologic users, where were using AWS, were using Azure and the rest are spread across the other cloud service providers (CSP) or using . Here are the key takeaways from the document: 64% 3.8% multi-cloud strategy of AWS users leverage Linux OS. The numbers of Linux OS users on Azure tripled from **4%**in 2016 to in 2017 80% 12% AWS Lambda adoption grew nearly (from 12% in 2016 to 23% in 2017) 200% of AWS users use Docker in 2017 (growing from 18% in 2016) 24% databases are now more popular than traditional . In fact, Redis, MongoDB, and Cassandra ( ) just overtook the MySQL, PostgreSQL, and RedShift ( ). These 2 groups comprise of all databases used on AWS, with Oracle and Microsoft SQL lagging significantly. NoSQL RDBMSs 28.3% 27.3% 55.6% and lead the way as web servers, with IIS falling behind. NGINX Apache is the #1 reason for cloud transition, yet nearly of AWS customers the built-in AWS CloudTrail service. VPC Flow Logs tools for monitoring the AWS VPC traffic were also quite seldom used, with only of the respondents confirming their adoption. Security 50% did not ever use 14.1% Final thoughts on the state of DevOps adoption The statistics from the reports above clearly indicate that the companies that do undergo the DevOps adoption see significant improvements in their software delivery practices and are able to achieve their intended business goals. However, cultural traditions are harder to break and unless a true collaboration and knowledge sharing take place — certain challenges arise. Overcoming these challenges is but a question of time, of course. Yet this means even the companies that have currently not begun their transition to DevOps can still succeed and gain the competitive edge over the rest of market players in their industry. They just should accept the DevOps adoption wholeheartedly, allocate their resources efficiently and build better, more streamlined and automated workflows. If you are one of the companies aiming to begin their DevOps journey and need some guidance — , we are always glad to help! give us a nudge This story was originally published on my . company’s blog
