Different Phases of Azure Migration

What are different phases of Azure Migration

What are different phases of Azure Migration

 

In this blog post I will explain you about, What are different phases of Azure Migration I will try to be as short as possible while explaining things and make sure you get the crust of the entire topic in this same very page.

Azure Migration can be boiled down to three main phases as shown below

Different Phases of Azure Migration
Different Phases of Azure Migration

Phase 1: Iaas (Infrastructure as a Service)
Phase 2: Paas (Platform as a Service)
Phase 3: SaaS(Software as a Service)

In the initial phase where your management has decided to move to cloud to save more on operational costs Its always advisable to move your on-prem infrastructure step by step. It can again be done parallel with the help of asynchronous replication to your cloud data center.

In the diagram below I will show you the terms used for each stage of migration, such as Re-host, Refactor, Re-architect, Rebuild and Replace.

What are different phases of Azure Migration
What are different phases of Azure Migration

 

Now Lets understand about each stage in a little more detail:

Rehost

Rehost Stage of Azure Migration

 

 

Re-host is also known as “lift and shift” stage. In this stage you migrate your physical servers and virtual machine as-it-is to the cloud by simply shifting your current server environment straight to IaaS. As you see in the picture on your right you can see only the operating system and the hardware is something which is managed by the cloud provider <Azure> and rest of the things like app data, code, app configuration, app platform and containers are still maintained and managed by you this is the most popular migration approach and it lets the organization move quickly with little risk. In the next stage will talk about Refactor stage.

 

 

Refactor

Refactor Stage of Azure Migration

 

 

 

Refactor stage is also known as “repackage”, in this stage two more services are used from Azures stack to optimize the cost. as you will see in the picture on your right you are using containers and App platform apart from OS and the hardware by making some minor changes in your application code or configuration which lets you connect your application to new infrastructure services such as containers, database and identity management systems.


Rearchitect

Rearchitect Stage of Azure Migration

 

 

Rearchitect stage is also known as “redesigning” when you say redesigning it means you’re redesigning the application to modernize it using a modular architecture. As you will notice on your right in the previous stage we were just updating the code and application configuration however, in this rearchitect stage we are getting a new code and app configuration. however, the hardware operating system containers an app platform would be managed by the cloud provider and rest API error code in app configuration would be managed by you.

 

Rebuild

In this stage customer tend to revise the existing application by aggressively adopting PaaS or even SaaS. In this process major revisions are done to add new functionality in the application for the cloud.

Replace

Replace Stage of Azure Migration

 

This stage refers to moving or discarding existing application and replacing it with Azure services. When you choose this option, all underlying infrastructure are managed by Azure, see the picture on your right for detail.




Search blogs




Bitnami