Products + Services Data Centers Network Industries Learn About
Whether you’re interested in testing out the cloud with a few workloads or are executing a full-scale cloud migration, you must determine which workloads will go first. But don’t just randomly pick a few.
Workload Assessment
Before deciding which workloads to move and which will go, inventory and assess them as part of your cloud migration strategy. For each workload, determine the following:
Once you understand your workloads, you can assess their suitability for moving to the cloud, what will be required and which should move first.
As you flesh out your cloud migration strategy, it’s important to note that not all workloads can or should be moved to the cloud. Once you’ve determined which ones they are, put them at the bottom of your “move-to-the-cloud” workload list.
Keep in mind that some workloads require modification before they can move if they’re to perform optimally in the cloud and take advantage of what the cloud has to offer. Some require more work than others, so the time and cost of preparing them come into play. Others may not be appropriate for moving at all.
For example, you may have obsolete (or soon will be) applications that should either be retired and/or replaced. Some may be tied to highly customized, internal legacy equipment that would make it difficult for them to move.
Many legacy applications were designed and developed for on-premises infrastructure and aren’t designed to run in a cloud environment. This can lead to compatibility issues when trying to migrate them.
Then there are the workloads with high-performance computing (HPC) demand real-time data processing and heavy computational power with low-latency communication requirements between nodes. They may not perform well in the cloud, and their significant resource requirements can quickly increase costs – canceling out the cost benefits of moving to the cloud.
Data-intensive workloads may not be good candidates either. They tend to generate large amounts of data that are often best analyzed and processed close to where they are generated. This can be difficult to achieve in the cloud, particularly if the data is generated on-premises or in a different cloud region.
Another consideration: cloud service providers (CSPs) usually charge for data egress ─ the transfer of data from the cloud to external systems or networks. Costs can add up for data-intensive workloads that involve transferring large amounts of data between the cloud and on-premises systems or between different cloud regions.
Compliance-driven regulatory workloads may not be optimal for cloud migration in some cases as well. Although CSPs offer robust security measures, some organizations may be more comfortable keeping their data on-premises, where they can have full control over security.
Cloud-native applications were written for the cloud – no problem there regarding their suitability for moving. But what makes a workload “cloud ready”?
A cloud-ready workload has been modified ─ refactored or re-platformed ─ to run in the cloud. Workloads that will require modification before they can move, particularly if it will be extensive, usually won’t be among the first to move. However, they should still be assessed and prioritized to ensure they’re ready to move when you’re ready to move them.
What Workloads to Move First
Once you know what workloads can, can with some work, can’t, and shouldn’t move to the cloud, you can prioritize them.
What specific workloads do most companies move first? It varies, but many choose to move backups, disaster recovery, and batch processing workloads first.
Applications used by mobile employees to manage their time and activity and that contribute only limited information to the company’s broad management information databases are also popular choices. Email is a good choice as well. (Surprisingly, many businesses are still utilizing in-house email servers.)
The cloud may also be appropriate for developing, testing, and prototyping application changes, even if the final app will run on your own infrastructure.
Additional Cloud Migration Resources
To learn more about prioritizing workloads to move as part of your cloud migration strategy – and about cloud migration strategies in general, check out these articles below from our blog or visit our resource center for whitepapers, e-books, and more!
How Much Does It Cost to Move to the Cloud?
Cloud Migration: Measuring Success
10 Steps for More Successful Cloud Migrations
Q&A on Cloud Migrations with Daven Winans
In the rapidly evolving landscape of cloud computing, Chief Information Security Officers (CISOs), Chief Information Officers (CIOs), and Chief Technology Officers (CTOs) of mid-market businesses and medium enterprises find themselves at a crossroads. The unpredictable price increases from VMware have shaken the industry, [...]
Introducing OpenCloud If you’re here, it’s likely that you’ve heard by now the announcement of our new Infrastructure-as-a-Service hosting product, OpenCloud. If not, check out the Press Release here! The purpose of this post is to tell the story of OpenCloud and our customer lead development process, as well as to [...]
With the public release of OpenCloud last week, I wanted to share our strategy for US Signal Cloud products. The launch of OpenCloud was to provide another option in an expanding landscape of cloud and virtualization solutions, offering a predictable cost model and native cloud features such as self-provisioning, [...]