Provisioning And Migrating Cloud Resources
Provisioning & Migrating Cloud Resources
Every cloud deployment starts the same way: compute, storage, and network, sized to fit a budget and a compliance sheet. Getting there from where you are now is its own decision tree — on-prem to cloud, cloud to cloud, or somewhere in between.
Provisioning a Cloud VM
Deploying cloud resources usually begins with a virtual machine. Every VM needs three things — compute, storage, and network — and the exact configuration is a trade-off between performance, compliance, security, and cost. Drag the sliders to see how a configuration shifts.
Migration Paths
The standard route is on-premises to cloud. But once a workload already lives in one cloud, organizations sometimes move it to another provider entirely, chasing better pricing or a feature the current provider lacks.
The standard migration path. Physical or virtual servers running in a private data center move to virtual machines hosted by a cloud provider — trading owned hardware for rented, elastic capacity.
How Much Does the Application Itself Change?
Moving the infrastructure is one decision. What happens to the application running on it is another — and it ranges from barely touching the code to deleting it outright. Click a stop along the line.
Rehost — "lift and shift"
The application moves to cloud VMs with little or no code change. It's the simplest, fastest migration, and the default choice when the app already runs fine and there's no pressing reason to touch it.