Cloud-Native Release Orchestration 2021 - THE STATE OF - the State of Cloud Native Release Orchestration 2021
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
THE STATE OF Cloud-Native Release Orchestration 2021
Table of contents
Key takeaways …………………………………………………………………………………….. 3
Survey demographics ………………………………………………………………………… 4
Cloud-Native technology stack ………………………………………………………… 6
Business drivers for Cloud-Native technologies …………………………… 7
Releasing in production …………………………………………………………………….. 8
Most used monitoring tools ………………………………………………………………. 9
Release validation ………………………………………………………………………………. 10
Rollback of releases ………………………………………………………………………….. 11
Key metrics per industry and company size …………………………………. 12
Responsibilities ………………………………………………………………………………….. 13
Releasing microservices is not without challenges ……………………… 14
Focus for improvements in 2021 …………………………………………………….. 16
About Vamp …………………………………………………………………………………………. 17
| State of Cloud-Native Release Orchestration 2021 P2Key takeaways
1 Kubernetes and microservices have become
mainstream. 72% uses Kubernetes and 81% uses
microservices in production today.
4 53% of rollbacks are done manually with an
average time to rollback of 45 minutes.
2 86% of participants are still using high-risk release
strategies such as rolling update, blue-green and
big-bang releases.
5 Dependency management is the biggest
challenge regarding releasing microservices in
production.
3 Validation of released software in production
remains a manual task. On average it takes 2.2
hours with 4 people engaged per release.
6 Self-service deploy and release automation
capabilities are needed to support the shift-right
movement of developers.
| State of Cloud-Native Release Orchestration 2021 P3Survey demographics 1/2
In total we surveyed 253 developers, DevOps, SREs, engineering RESPONSES BY INDUSTRY
managers, architects and C-level executives across the world to
uncover trends, challenges and opportunities for improvement Software / Technology / ISV 37%
when it comes to releasing and validating software in production.
Financial services 25%
Telecommunications 11%
RESPONSES BY REGION Retail / e-Commerce 6%
Europe
Healthcare 4%
71%
Media / Entertainment 4%
Other 13%
U.S & Canada
Asia
24%
3% RESPONSES BY COMPANY SIZE
1 - 100 21%
101 - 1000 23%
South-America Other
1001 - 5000 14%
1% 1%
5000 + 42%
| State of Cloud-Native Release Orchestration 2021 P4Survey demographics 2/2
C-level
3%
SRE
7%
Development
24%
Other
5%
DevOps
44% IT Architecture
10%
IT Operations
7%
| State of Cloud-Native Release Orchestration 2021 P5CLOUD PROVIDERS
Cloud-Native technology stack
Kubernetes and microservices have become mainstream. 72% of 34% 15% 14%
participants say that they are using Kubernetes in production today
and 16% says that they are evaluating or planning to use AWS Hybrid Cloud Azure
Kubernetes. Microservices are even more popular. 81% of
participants say that they are using microservices in production
today and 14% says they have plans to use microservices. 13% 10% 14%
On-prem Google Cloud Other
KUBERNETES MICROSERVICES
5%
12% We depend on Kubernetes We depend on microservices
6%
in production today in production today
5% 8%
We have our first Kubernetes We have our first microservices
clusters in production in production
11%
We are evaluating Kubernetes We are developing microservices
50% and it’s not in production but it’s not running in production
19%
We are planning to implement 62% We are planning to develop
Kubernetes, but haven’t started microservices, but haven’t started
22% We don’t have Kubernetes and We don’t have microservices and
have no plans for them have no plans for them
| State of Cloud-Native Release Orchestration 2021 P6Business drivers for Cloud-Native technologies
Improve internal culture and collaboration
6%
Better maintainability of software
19% Improve performance and scalability
35%
23%
Improve development speed and faster time-to-market
17%
Deliver a better customer experience
| State of Cloud-Native Release Orchestration 2021 P7Releasing in production RELEASE STRATEGY
Releasing in production is the process of taking
running code and making it “live” and accessible 57% 22% 9% 7%
to users, in a predictable and repeatable way. It's
about paying particular attention to ensure that
releasing a new version doesn’t result in a worse Rolling update Blue-green Canary Big-bang
experience for your users.
RELEASE FREQUENCY LEAD TIME TO PRODUCTION
Key insights:
34% 33%
• Majority of participants are still using high-
risk release strategies like rolling updates, 29% 23%
22% 19%
blue-green and big-bang releases. 12% 11% 13%
• Lack of canary releasing capabilities. 3% 1%
• 68% of participants are releasing on a weekly
Yearly Monthly Weekly Daily On-demand Years Months Weeks Days Hours Mins
or daily basis.
Companies with a daily release Companies with a weekly/monthly
frequency have an avg. lead time release frequency have an avg. lead
to production of hours time to production of weeks
| State of Cloud-Native Release Orchestration 2021 P8Most used monitoring tools
APPLICATION PERFORMANCE MONITORING TOOLS
In this survey, we asked what monitoring tools
are being used to validate releases and updates 18% 18% 17% 16%
in production to ensure health, performance and
quality. Please note that participants may use one
or more tools. Dynatrace Datadog New Relic AppDynamics
LOG ANALYTICS TOOLS
Key insights:
• The data from monitoring tools is not integrated 56% 35% 21%
and actionable in the release pipeline.
• Elastic and Prometheus are widely used by Elastic Splunk FluentD
participants to validate releases in production.
• Released microservices are often monitored
CLOUD/INFRA MONITORING TOOLS BUSINESS MONITORING TOOLS
from a technical perspective (response time,
latency etc.), but rarely from a business
perspective (user experience, orders per second, 57% 28% 30% 23%
shopping basket value etc.).
Prometheus Cloud Watch Google Analytics Don’t use any
| State of Cloud-Native Release Orchestration 2021 P9Release validation AVERAGE AMOUNT OF PERSONS INVOLVED WITH RELEASE VALIDATION
35%
Release validation is the process of making sure
that released software that’s running in 18%
15%
production is meeting the requirements in terms 12% 11%
of performance, quality, customer experience and 4% 5%
business KPIs.
1 person 2 persons 3 persons 4 persons 5 persons 6 persons Don’t know
or more
Key insights: AVERAGE TIME SPENT ON RELEASE VALIDATION
• The validation of released software in 19% 21%
14% 13% 16%
production remains a manual task. 10% 7%
• On average it takes 2.2 hours with 4 people
engaged during the release validation process. 0 - 0.5 hour 0.5 - 1 hour 1 - 2 hours 2 - 3 hours 3 - 5 hours 5+ hours Don’t know
• Teams that have a higher release frequency are
spending less time on validation per release.
228 min
168 min
142 min
112 min
Time spent on
90 min release validation
Releasing multiple Daily Weekly Monthly Yearly
times per day releases releases releases releases
| State of Cloud-Native Release Orchestration 2021 P10Rollback of releases 87% of participants are using
a rollback strategy 13% of participants are using
a roll-forward strategy
Rollbacks are a critical part of your release
strategy. When implemented right, it creates a 74%
safety net to protect your software teams and 53%
minimize the impact on the customer experience 39%
26%
when issues are starting to occur.
8%
Manual Automated Reactive Proactive
Both
rollback rollback rollback rollback
Key insights:
• There is a lack of automation in the rollback
process. 53% is still doing manual rollbacks. TIME TO ROLLBACK AFTER EXPERIENCING ISSUES
• Only 26% of rollbacks are proactive and are
26% 18%
used to prevent issues in production. 15%
10% 10% 12%
• Average time to rollback is 45 minutes.
2% 3% 4%
0 minutes 0 - 15 min 15 - 30 min 30 - 60 min 1 - 2 hrs 2 - 3 hrs 3 - 4 hrs 4+ hrs Don’t know
Average time to rollback in Average time to rollback in
41 65 a monolith-based
a microservices-based min
min environment environment
| State of Cloud-Native Release Orchestration 2021 P11Key metrics per industry RELEASE FREQUENCY PER INDUSTRY
and company size 43% 48%
36% 31% 31% 37%
26% 21% 24% 21%
18% 15%
Let’s have a look at some of the key release 10% 11% 12% 7% 3% 2% 4% 0%
metrics per industry and company size. In this Multiple times per day Daily Weekly Monthly Yearly
analysis, we’ve focussed on four industries:
Computer Software, Financial Services, Technology / Computer Software Financial Services Telecommunications Retail / e-Commerce
Telecommunications and e-Commerce.
RELEASE FREQUENCY PER COMPANY SIZE
Key insights:
37% 35%
• Retail and e-Commerce companies most
27%
18% 11% 13%
31%
21%
4% 3%
often release to production. 43% say they
Multiple times per day Daily Weekly Monthly Yearly
release multiple times per day.
• Small and medium-sized businesses have a SMB (0 - 1000 employees) Enterprise (1000+ employees)
slightly higher release frequency compared to
enterprise
OTHER REMARKABLE OUTCOMES
• 50% of e-Commerce companies say that
better maintainability of software is their #1
50% of e-Commerce companies say that 93% of companies in the Telecom
reason to go cloud-native. Only 7% focusses better maintainability of software is their industry say that they use
#1 reason to go cloud-native microservices in production
on improving the customer experience.
| State of Cloud-Native Release Orchestration 2021 P12Responsibilities
You build it, you run it. Developers are getting more responsibilities and are more
engaged with the day-to-day operations of their software. 34% of participants
say that their developers are not only responsible for building features, but also
for making sure it’s released to end-users in production. The question is: how
are you enabling your developers in this shift-right approach?
WHO IN YOUR ORGANIZATION IS RESPONSIBLE FOR THE WHO IN YOUR ORGANIZATION IS RESPONSIBLE FOR
PROCESS OF RELEASING NEW SOFTWARE INTO PRODUCTION? MONITORING PRODUCTION ISSUES AND/OR OUTAGES?
Other Other
3% 5%
Quality & Assurance Quality & Assurance
2% 4%
DevOps
DevOps 28%
Developers
33%
18%
Developers
34%
Product Management
3%
Release Manager SRE
SRE 1%
Product Management 14%
7%
2% IT Operations
IT Operations 27%
Release Manager 6%
13%
| State of Cloud-Native Release Orchestration 2021 P13Releasing microservices is not without challenges 1/2
Here are the top three biggest challenges regarding releasing
microservices in production. Please note that we’ve used an
open question.
11 Dependency management 20%
22 Internal processes
and communication
14%
Nearly 9 in 10 report challenges and issues
when they release microservices
to production
33 Validating changes and
testing of microservices
10%
| State of Cloud-Native Release Orchestration 2021 P14Releasing microservices is not without challenges 2/2
Here’s what some of our participants are saying about their
biggest challenges regarding releasing microservices in
production.
“ Impact on
various chains
”
“
“ Dependency
chain/hell
Testing the new features and validating
the integration with other microservices
“ Ensuring that they can be indeed
” released independently
” ”
“Uncertainty of non-functional behaviour
“ To make sure that communication
especially under load or outages
works between microservices “
”
Validating all services in
”
production still work
“ Managing microservices: as the number
”
increase managing gets challenging
“ Difference in data between pre-prod & prod sometimes
”
messes up the release with actual customer data
| State of Cloud-Native Release Orchestration 2021
” P15Focus for improvements in 2021
The results are clear. 30% of participants say that they would
like to focus on automating the Continuous Delivery and
Release processes within their organization. Automation
ensures that quality software is released at the speed the
business desires and needs to stay ahead.
15%
5%
Testing Internal
processes
30%
Continuous Delivery &
Release Automation
11% 6%
Continuous
Monitoring & Integration
Observability
| State of Cloud-Native Release Orchestration 2021 P16About Vamp
Vamp is a Cloud-Native AIOps platform that provides self-
service release automation and cost optimization capabilites.
Vamp automates the release process, applies a safety net when
releases fail and pinpoints the precise operational capacity
needed to run an individual service – all while safeguarding the
customer experience.
Vamp is trusted by leading companies across the globe to
automate and accelerate their Go-Live process.
Go to vamp.io to learn more and request a demo.
| State of Cloud-Native Release Orchestration 2021 P17Release with confidence - Even on a Friday afternoon
You can also read
