I’m Over Here Now: Moving Azure Services to a New Region
The cloud is touted as the final destination for many application environments, but while we imagine that we can just put the content and data into the cloud, there are valid reasons why data locality and geo-location will come into play for application owners.
One Cloud, Many Regions
Microsoft Azure is made up of numerous regions, each with their own subset of services that are available. This is usually based on demand by the customers within that region. Let’s imagine that we have an application that is gaining traction in a new part of the world, but response times are more challenged because they are hosted outside of that physical region.
Remember that cloud is a methodology, not a location. So how do we migrate or copy data from one region to another? There are actually a few ways to take on the task, and luckily the team at the Azure blog did a really good job of describing a viable solution to a realistic scenario.
You can read their article here which will give an inside look to the thought process of how to create the ideal data movement methods. Good food for thought as you build out your application in Microsoft Azure.