More and more organizations are turning to public cloud due to their benefits such as on-demand, self-service access, nearly unlimited capacity, large-scale infrastructures, operational best practices, and pay-as-you-go pricing. However, not all workloads are suited for the public cloud. Incredibly short and fast on-ramp can be a downside as well. Find out in this article, where you’ll discover seven considerations for migrating and running your workloads in public cloud.
The reality is that, for most organizations today, running a small, simple application on one public cloud may be a first step but it isn’t the ultimate—or even a mid-term—goal. That goal is more nuanced, more complex. That goal is to reliably run large, scalable applications made up of many loosely-coupled components. That goal is to maintain flexibility around where applications run—whether that means switching providers or running them on a mixture of in-house, dedicated external, or multi-tenant cloud resources. That goal is to make use of public clouds as part of a broader hybrid IT environment rather than a new silo of vendor lock-in.
So how do you move a workload (or write a new application) for a public cloud and meet that goal?
Many different factors come into play. However, based on a wide range of conversations with customers, partners, analysts, and others, we’ve developed a list of seven key considerations that are especially important and applicable to a broad range of situations:
- Developing an appropriate application architecture
- Maintaining portability of applications and workloads
- Ensuring data is portable
- Understanding legal and regulatory compliance
- Enabling hybrid cloud management, policy, and governance
- Isolating workloads as needed in a public cloud
- Providing access to standard languages, frameworks, and tools
