Traffic Dialing When Migrating Workload to Cloud

Workload migration from On-Premise to Cloud is getting common now a days. Teams are migrating their workloads because of multiple reasons. They prepare a huge migration checklist but one area where I generally see Teams having question is — How do we dial the traffic from On-Premise to Cloud — what all options do I have?

To be very honest, every Cloud Migration is unique in some or the other way. It comes with its own set of challenges. So, there is no silver bullet for the problem.

In this blog, I have tried to summarize some of the common patterns used for Traffic dialing.

1. All at Once
2. Tip-Toe
3. Time Based (leveraging the above 2 approaches with time duration)

Approach 1 — All at once — This is the easiest approach of moving the traffic from On-Premise to Cloud. It may or may not involve application downtime depending on external factors. For example, if there is an external tool being used for keeping the workload data in real time sync between On-Premise and Cloud, then it will not have any downtime. But if data is to be copied before migration to ensure data integrity, etc., then there will be some downtime involved and the duration of unavailability of the workload depends on the volume of data to be pushed to Cloud on the day of migration.

All at once Traffic Shift