6 captures
10 Aug 2023 - 25 Jul 2025
Jul
AUG
Sep
10
2022
2023
2024
success
fail
About this capture
TIMESTAMPS
The Wayback Machine - https://web.archive.org/web/20230810204022/https://devops.com/improved-observability/
DevOps.com
Latest
Articles
Features
Most Read
News
News Releases
Topics
AI
Continuous Delivery
Continuous Testing
Cloud
Culture
DataOps
DevSecOps
Enterprise DevOps
Leadership Suite
DevOps Practice
ROELBOB
DevOps Toolbox
IT as Code
Videos/Podcasts
Techstrong.tv Podcast
Techstrong.tv - Twitch
DevOps Unbound
Webinars
Upcoming
Calendar View
On-Demand Webinars
Library
Events
Upcoming Events
Calendar View
On-Demand Events
Sponsored Content
Related Sites
Techstrong Group
Cloud Native Now
Security Boulevard
Techstrong Research
DevOps Chat
DevOps Dozen
DevOps TV
Techstrong TV
Techstrong.tv Podcast
Techstrong.tv - Twitch
Media Kit
About
Sponsor
AI
Cloud
CI/CD
Continuous Testing
DataOps
DevSecOps
DevOps Onramp
Platform Engineering
Sustainability
Low-Code/No-Code
IT as Code
More
Application Performance Management/Monitoring
Culture
Enterprise DevOps
ROELBOB
Hot Topics
Data Management: Cloud Technology or Data Centers?
Low-Hanging Fruit, 2023 Edition: Part One
DevOps World: Time to Bring the Community Together Again
DevOps Guide to the Salesforce Summer 2023 Release
4 Salesforce DevOps Adoption Challenges
Improved Observability
Improved Observability
By:
ROELBOB
on
July 31, 2023
« 4 Things Engineering Leaders are Thinking About Right Now
A Distributed Workforce is the New Normal »
Workload Portability PulseMeter
Step
1
of
7
14%
Do you expect to move workloads between cloud providers?
We are doing this now
Within 6 months
Between 6 months and 1 year
Between 1 year and 2 years
More than 2 years
We have no plans to move cloud workloads
Why do you need workload portability? (Select all that apply)
Disaster recovery/business continuity (recover in the event of an outage)
Resilience (to ensure no downtime)
Reduce latency (move workloads closer to the user)
Performance (move workloads to a platform optimized for a workload. e.g., analytics)
Scalability (Better support for rapid scaling)
Cost savings (utilize lower-cost cloud providers)
Take advantage of cloud native tools not offered by current cloud provider
Avoid cloud provider lock-in
Regulatory/Compliance (cloud provider does not have in-country site)
Do you plan to move workloads back and forth between providers, or is it a one-way porting effort?
We plan to move workloads back and forth
One-way porting effort
Both
None
What approaches do you take in application architecture to facilitate portability? (Select all that apply)
We use containers
We have adopted a microservices architecture
We deploy using infrastructure as code (IaC)
We select cloud agnostic/cloud native services (where possible)
We choose multicloud management tools
We adopt industry standards and open-source technologies
We plan for data migration/replication
We assess the differences in security between cloud providers
What is the biggest challenge you face in moving workloads?
Vendor Lock-in: Many cloud services use platform-specific tools. The use of such services can make it challenging to migrate workloads to a different cloud platform.
Data Migration: Transferring large volumes of data from one cloud provider to another can be a complex, time-consuming and costly process.
Incompatibility Issues: Each cloud platform has its own set of APIs, configurations, and services. Even if two platforms offer similar services, there can be differences in the specifics of how these services are implemented. These inconsistencies can pose challenges in maintaining the same functionality when moving workloads.
Security and Compliance Concerns: Each cloud provider has its own security features and controls. When moving workloads, organizations need to ensure that the new environment meets the same security standards and compliance requirements as the previous one.
Skills Gap: Each cloud platform requires a specific set of skills and knowledge. There may be a lack of expertise in the new cloud platform, leading to a steep learning curve for the team.
Do you agree with the following statements about data migration costs?
Strongly Disagree
Disagree
Neutral
Agree
Strongly agree
My organization factors data migration costs into workload architecture and planning.
My organization models data migration costs in the event the workload is moved.
My organization selects a cloud platform provider based on data migration costs.
My organization will not replatform a workload if the data migration costs are too high.
What is the size of your business or organization?
1 - 100 employees
101 - 500 employees
501 - 1000 employees
1001 - 5000 employees
Over 5000 employees
Δ