Moving Cloud Workloads: 4 essential strategies
How you place and move workloads among different environments should be a key part of your hybrid or multi-cloud strategy. Consider this expert advice.
Developing criteria for deciding what goes where
Many hybrid cloud and multi-cloud environments begin in an ad hoc or even accidental fashion. That’s natural, but they should eventually be replaced with – as Haff noted – a more intentional strategy.
That begins with having clear criteria for placing – and moving – workloads in a given environment.
“There are a lot of reasons to decide where to place a workload,” Matt Wallace, CTO at Faction. “The hard part comes when there’s no right answer because you have teams or partners in different clouds, or need access to different services.”
So focus on the tangible reasons that matter to you and let those guide your choices. Wallace shares several examples:
- Proximity to other apps and data – also known as “Data Gravity,” and often a driving factor whenever performance/latency is a major concern
- Collaboration with other teams & partners – if they use a particular cloud, it may make sense for you to as well
- The set of tools available in a particular cloud – they’re not all the same
- Geographic/locality concerns
- Cost (more on this below)
- Scale – such as the difference between a predictable, stable workload versus one that is likely to grow or have lots of spikes in resource demand
Read the full article here.
