DoK Report 2021
DoK Report 2021
DoK Report 2021
GOLD
SILVER
CIO/CTO 25
Developer/Software engineer
to use Kubernetes. This included an
6
Data scientist 5
international audience of 502 respondents.
DevOps 4
Business leadership
Because data on Kubernetes impacts a 3
Operations / Administrator 2
large part of an organization’s IT team –
Architect 1
from CIOs and CTOs, VPs and Directors of
IT, Software and Site-reliability engineers,
Database administrators, and Data ORGANIZATION SIZE
engineers – the targeted demographic ratio
is practitioners (~35%), managers (~20%), and 100 - 499 11
executives (~45%).
500 - 999 29
cloud world.
1%
19 %
31%
Australia & New Zealand
Europe
Asia
US & Canada
48 %
INDUSTRY
Telecommunications/ISP/
6 % Web Hosting
Other
1%
Education
1%
1% Infrastructure and Construction
1% Non-financial Services
3% Aerospace and Defense
IT
Financial Services
49 %
12%
Government
1%
Health care
4%
8% Manufacturing
and heavy industry
1% Media
5% 1% Primary goods
2%
Retail and wholesale Transportation and logistics
Before diving into the specifics of running data How much more productive is your
on Kubernetes, we wanted to understand how
organization/are your developers
organizations are using Kubernetes across
all workloads. We found that Kubernetes has after adopting Kubernetes?
become a core part of their infrastructure –
half of the respondents are running 50% or More than 2x more productive 5
Under 10%
The more Kubernetes is in use; the more
2
productive an organization is: when we look at
10% - 24% 13 Kubernetes Leaders – the 11% of respondents
running 75% or more of their production
25% - 49% 34
workloads on Kubernetes – they report even
50% - 74%
higher levels of productivity with a majority
39
achieving an impressive 2x or more productivity.
75% - 99%
10
100%
1
15
more productive after adopting Kubernetes. About 50% more
41
Unsurprisingly 68% say they are very likely to About 10% more
12
34
increase their Kubernetes footprint. 6
We are no more or less productive
1
In general, how satisfied are you with How likely are you to migrate
the use of Kubernetes for production additional production workloads to
workloads in your organization? Kubernetes in your organization?
25
Within the past 6 months
32
1-2 years ago
15
2 or more years ago
For those currently running stateful workloads in production, we see broad usage that maps closely to
overall Kubernetes usage in the previous section. Over half of this cohort (51%) intends to increase the
volume of workloads by 30% or more in the next 12 months. More Kubernetes = more productivity = high
satisfaction. See a pattern here? Kubernetes is here to stay.
10
10% - 24% 16
25% - 49% 35
50% - 74%
39
75% - 100% 7
70
26
Databases 50
Persistent storage 45
Streaming/messaging 45
Backup/Archival storage 45
Object storage 42
Analytics 39
AI/ML 38
When we look at Kubernetes Leaders, Databases remain in the top spot but become more important
– jumping 11% – while Persistent Storage becomes less important to this group, a reduction of 14%
compared to all respondents.
Databases 61
50
Backup/Archival storage 58
43
Streaming/messaging 45
44
Object storage 45
43
AI/ML 42
39
Persistent storage 35
49
32
Analytics
43
From the following, which are the THREE most important factors in your or-
ganization’s decision to run stateful workload(s) on Kubernetes?
Ensure Consistency 45
Standardizing on Kubernetes 40
Simplify Management 39
Enable Developers to
self manage 39
Enable hybrid/multi- 35
provider DBaaS
Reducing TCO 29
Auto-healing 22
This becomes even more pronounced when we look at responses from Kubernetes Leaders. Not only does
standardization jump 10 points, we also see security jump ahead of scalability, deployment, and other Day 1
benefits of Kubernetes. The more workloads an organization runs on Kubernetes, the more it can capitalize
on the standardization advantage.
Standardizing on Kubernetes 50
39
Ensure consistency 41
45
Enable hybrid/multi-provider 41
DBaaS 35
35
Auto-healing 21
32
Simplify management 40
24
Avoid Vendor Lockin 27
21
Reducing TCO 30
Looking ahead to a future where organizations can more seamlessly react to data in real-time, a
majority would like to see data become declarative, just like Kubernetes. Our next survey will delve
deeper into what will be required to create a language for declarative data on Kubernetes.
Much
Somewhat
Now you will see a series of pairs of statements. For each pair select the statement
that you agree with more, even if you agree with both a little.
Kubernetes Leaders face a different set of challenges with a four-way tie for first place: vendor solutions
solve niche needs, little or no vendor solutions exist, too much time and effort to manage, and lack of quali-
fied talent. The talent gap was the most drastic difference when compared with all respondents, jumping 11%.
35
Vendor solutions solve niche needs
34
35
Little or no vendor solutions exist
28
35
Too much time/effort to manage
26
35
Lack of qualified talent
24
Databases 52 32
Persistent Storage 43 38
Analytics 43 36
Backup/Archival storage 43 37
Object Storage 41 36
AI/ML
35 38
Streaming/messaging
33 37
Currently use Kubernetes operators for this Plan to use Kubernetes operators for this
The primary benefit of Kubernetes operators cited by respondents is that they simplify the
management of workloads in multi-cloud and hybrid cloud environments. Simplicity and scalability
also rank highly.
What would you say are the primary benefits of using Kubernetes
operators? (Select all that apply)
Scalability 49
Ability to customize 40
Elasticity 33
Self-healing 25
61
Difficult to maintain interoperability
50
with other operators
Lack of standardization 40
24
Seems like a workaround rather than a 37
clean technical implementation
Other
Further underscoring this point, lack of quality operators is cited as the number one reason preventing
some from using Kubernetes for stateful workloads – the 10% “non-believers” who do not think
Kubernetes is production-ready for running data.
44
31
31
29
27
19
Despite the challenges, respondents believe that running stateful workloads on Kubernetes is the way
forward as evidenced by the productivity and satisfaction gains we see in the first section. When asked
to envision a future that simplifies management and automation on Kubernetes, a 2:1 majority agree
that the standardization of data management is important.
35
35
17
Now you will see a series of pairs of statements. For each pair select the
statement that you agree with more, even if you agree with both a little.
Standardization is a recurring theme for our respondents. When done well, it drives Kubernetes
adoption; when absent, it slows it. This is even more pronounced for Kubernetes Leaders running
75%+ workloads in production – standardization jumps 11% to the top spot (up from number two for all
respondents), followed by consistency and the ability for developers to self-manage.
From the following, which are the THREE most important factors in your
organization’s decision to run stateful workload(s) on Kubernetes?
50
Standardizing on Kubernetes
39
41
Ensure Consistency
45
41
Enable Developers to self manage
40
41
Enable hybrid/multi-provider DBaaS
35
Auto-healing 35
21
32
Simplify Management
40
24
Avoid Vendor Lockin
27
21
Reducing TCO
30
Real-time data will increase the demand for running data on Kubernetes
Much
Somewhat
Going forward, how companies leverage Real-time data is useful but other
their real-time data is the key to factors will be more important to
competitive advantage. competitive advantage
Now you will see a series of pairs of statements. For each pair select the
statement that you agree with more, even if you agree with both a little.
Kubernetes Leaders are also more interested in running AI/ML workloads than all respondents,
jumping to the #2 position behind databases (up from #6) – an indicator of what the future of
DoK may look like for all.
Conclusion
Stateful workloads are pervasive, and the most advanced Kubernetes users benefit from massive
productivity gains thanks to the standardization of how they run stateless and stateful workloads. The
operator pattern is beneficial, but not without challenges which is forcing organizations to build their
own. Standards and/or best practices are needed to bring operators to a level of quality that will allow
organizations to realize the benefits of running stateful workloads in a consistent way.
Signs point to a future where organizations can standardize, or further standardize, on Kubernetes for
data-intensive workloads. This may be driven by industry standards and exemplified by declarative
data and similar concepts. It will undoubtedly encompass the world of data technologies (persistence,
streaming, analytics), data infrastructure (storage, security, networking), and data governance (pol-
icies, protocols, access) and require contributions from everyone; achieved with open communities,
open standards, and open source. The future is ours to build.