6 Interesting Trends from the Latest CNCF Survey

DZone 's Guide to

6 Interesting Trends from the Latest CNCF Survey

The Cloud Native Computing Foundation (CNCF) conducted another survey late last year and the results are now out. Here's what's popular in cloud native development.

· Cloud Zone ·
Free Resource

The latest annual CNCF Survey is out – the 7th of its kind – and it paints a truly positive picture of the cloud native marketplace.

According to the survey, which 1,337 CNCF community members around the globe responded to, the use of cloud native projects in production continues to grow. Naturally the respondents are an audience who are more likely to be using CNCF related technologies, but it still makes interesting reading. The survey was only conducted in English, which may have led to the majority of European and North American respondents. With only 17% of respondents from Asia, but with a huge cloud infrastructure industry in Asia, I wonder if the statistics would be different had the CNCF conducted the survey in other languages.

Here are six of the report's highlights, find the full survey results on the CNCF website.

1. Containers have become the norm

The CNCF survey shows that 84% of respondents are using containers in production – a significant increase from the 73% doing so in 2018. In fact, in addition to expanding in production environments, container usage has also increased across development, testing, and all stages of the development workflow – a reality that highlights the increased trust organizations have in containers, and how they find increased applicable use from them.

2. Kubernetes Remains on Top

Compared to 2018, Kubernetes usage in production has risen dramatically, with 78% of respondents indicating they use it in production – a significant increase on last year's 58%.

Furthermore, while most users have a modest 2-5 clusters running in production (43%), just over 10% are running more than 50 production clusters!

3. Public Cloud Still the Most Popular

In 2018, public cloud was the most popular hosting approach, with 77% of organizations utilizing it. This remained the case in 2019, with public cloud the primary infrastructure choice for 62% of respondents. One potential reason for the decline is because the survey added hybrid cloud as an option in the most recent survey, and 38% of respondents selected it.

4. Service Mesh Adoption Still in Infancy But Showing Promise

This year was the first that respondents were quizzed about their adoption of service meshes. While only 18% said they were using service meshes in production, a further 47% said they were currently evaluating the technology for future use.

In terms of the most popular service mesh platforms, Istio, Consul and Linkerd topped the list.

CNCF said service mesh technology was still relatively new, and it would expect usage in production to increase over the next few years.

5. Daily Release Cycles Are on the Up

The number of respondents with daily release cycles jumped from 15% in 2018 to 27% in 2019, while weekly release cycles increased from 20% to 28%. Hybrid models are also up in 2019 to 41% compared to 25% in 2018. CNCF attributes this to an increase in both the number and reliability of CI/CD tools, the most popular of which are Jenkins (58%), GitLab (34%), and CircleCI (13%).

6. Serverless in Flux

The numbers of respondents using serverless is up slightly on 2018, with most using hosted platforms (lambda by far in the lead), and less people considering use the practise in the future. Maybe serverless has reached its pinnacle, or maybe the predominant tie to hosted platforms puts off other photo entail users.


Cloud computing, container-based development has become the norm against most development teams around the world, with numbers of users continuing to rise, and consolidate on certain tools. What do you use, and what are you looking to use in 2020?

kubernetes ,service mesh ,containers ,cncf ,cloud native ,serverless

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}