Data center migration into cloud

Make as few changes during the migration as possible, redeploying applications to the cloud without making substantial changes to how they are configured. It is the most straightforward cloud migration strategy where administrators just “lift” their applications, workloads, virtual machines, and server operating systems and “shift” them to the new operating model in the public cloud. 

The next step from a rehosting strategy, lifting the existing workloads and then optimizing them for the new cloud environment. For instance, a service may replatform a workload to the cloud to be able to take advantage of cloud-based microservice architecture, or containers in Kubernetes Engine. These applications will now have higher performance and more efficiency running in the cloud.

Taking applications and re-engineering them to be cloud-native, often changing the code of an application without altering its front-end behavior or experience. For example, a refactored application may be broken up from long strings of code into more modular pieces that can better take advantage of cloud capabilities, thus improving the performance of the code. 

Similar to refactoring but instead of restructuring how the application’s code works, it changes how that code functions in order to optimize the application and take advantage of cloud-native properties like scalability, security, and agility. One example of re-architecting an application is to take one large, monolithic application and turn it into several independent microservices. 

Take an application and rewrite it entirely for the cloud. It is often easier to build an application from scratch than it is to refactor its old code to work in a cloud environment. A rebuilding strategy allows an organization to plan from the ground up, choosing which cloud-native tools and capabilities to utilize from the beginning.