This article summarizes findings from the Logz.io DevOps Pulse 2017 survey, originally reported by SD Times on July 29, 2017.
DevOps Awareness Does Not Equal DevOps Adoption
DevOps has become a widely recognized term in the software development and IT operations space, yet widespread recognition has not translated into widespread adoption. The Logz.io DevOps Pulse 2017 survey — released to coincide with SysAdmin Day — polled 700 companies to understand the state of DevOps adoption, implementation challenges, culture, and infrastructure trends.
One of the most striking findings: roughly 50 percent of respondents were either still in the process of implementing DevOps or had only completed implementation within the past year. For a practice that has been discussed and promoted since at least 2009, this figure underscores how significant the gap between awareness and practical adoption still was in 2017.
Top Challenges: Culture, Communication, and Silos
The survey identified three leading cultural challenges that organizations face when trying to establish DevOps practices:
- Shifting company incentives to change behaviors — Getting teams to align around shared goals rather than departmental metrics.
- Maintaining open communication and transparency — Breaking down the information barriers that naturally form between teams.
- Building flexible processes — Moving away from rigid, siloed workflows toward iterative, collaborative ones.
“These three actions — among others — are often tied to the fact that it is very hard to escape the typical silos that develop within companies and teams. Everyone and every team has a different way of working and a different set of priorities to address, and goals to meet.”
— Logz.io DevOps Pulse 2017 Survey
Organizational silos remain one of the most persistent obstacles to DevOps success. When development, operations, security, and QA teams operate with separate toolchains, incentives, and reporting structures, the collaborative culture that DevOps depends on becomes very difficult to establish.
The Biggest Barriers Are Practical: Time and Expertise
While cultural issues are significant, the survey found that the top two reported problems with DevOps implementation were more practical in nature:
- Lack of time — Teams are already stretched thin managing existing systems, leaving little bandwidth to invest in transformation initiatives.
- Lack of expertise — DevOps requires a broad skill set spanning automation, CI/CD pipelines, cloud infrastructure, monitoring, and cultural change management. Finding or developing that expertise is a real constraint for many organizations.
These barriers are interconnected: organizations without DevOps expertise take longer to implement practices correctly, which further compounds the time problem. This creates a cycle that is hard to break without dedicated investment and executive buy-in.
Burnout Is a Growing Concern
The pressure of DevOps transformation is having a measurable impact on individual practitioners. According to the survey:
- About 40 percent of respondents said they feel moderately under pressure at work on a day-to-day basis.
- Fewer than 10 percent reported feeling extremely pressured daily.
- However, 70 percent said they could see themselves burning out at some point.
This gap between current stress levels and anticipated burnout is notable. It suggests that while many practitioners are managing today, they do not see the current pace as sustainable — a warning sign for organizations that depend on retaining skilled engineers.
Cloud Infrastructure: The Rise of the Big Three
The survey also tracked infrastructure trends, specifically the growing dominance of the three major public cloud platforms: AWS, Microsoft Azure, and Google Cloud Platform.
Comparing year-over-year data from the DevOps Pulse reports:
- In 2016, 28 percent of respondents used a cloud platform outside of the Big Three.
- In 2017, that figure dropped to just 13 percent.
AWS continued to lead the pack in overall adoption. The consolidation around a small number of hyperscale providers reflects both the maturity of these platforms and the increasing availability of managed services that reduce the operational overhead of self-hosting or using smaller cloud vendors.
Cloud Cost Management Is a Priority
While the initial driver for cloud adoption was often cost reduction, the survey found that cloud spending remains a significant concern as infrastructure scales with the business. Respondents mentioned a variety of cost management approaches, including platform-native tools, third-party cost management platforms, and custom-built solutions.
Approximately 70 percent of respondents said their primary goal with cloud cost management was to optimize their environment — not simply to cut spending, but to ensure they were using cloud resources efficiently and appropriately.
Key Takeaways for DevOps Teams
- Adoption lag is real. Even in 2017, half of surveyed organizations were still in early-stage DevOps implementation. Transformation takes years, not months.
- Culture is hard, but practicalities are harder. Time and expertise constraints block progress even when cultural intent is present.
- Burnout risk is high. Sustainable DevOps transformation requires realistic workloads and organizational support for practitioners.
- Cloud consolidation is accelerating. AWS, Azure, and GCP are capturing an increasing share of enterprise infrastructure workloads.
- Cost visibility matters. As cloud spending grows with the business, investment in cost management tooling pays dividends in efficiency and predictability.
Source: SD Times reporting on the Logz.io DevOps Pulse 2017 Survey. Original article published July 29, 2017.