Geo-Load Balancing with the Azure Traffic Manager

added by bradygaster
10/11/2011 10:47:33 AM

275 Views

When you deploy a typical web role in Azure, each instance is automatically load balanced at the datacenter level. The Azure Fabric Controller manages upgrades and maintenance of those instances to ensure uptime. But what about if you want to have a web solution closer to where your users are? Or automatically direct traffic to a location in the event of an outage? This is where the Azure Traffic Manager comes in, and I have to say, it is so easy to set up – it boggles my mind that in today’s day and age, individuals can prop up large, redundant, durable, distributed applications in seconds that would rival the infrastructure of the largest websites.


4 comments

dpeterson
10/11/2011 10:49:11 AM
That's very slick, normally you'd have to work with several cdn's and whatnot to get that level of distribution. I'm not sold on cloud computing as a panacea, but for something like this it really shines.

vijayst
10/11/2011 9:36:24 PM
I am not sure if the traffic manager really works well. How many data centers does Azure have? I believe it is mostly focussed on North America. If a user from India browses to an Azure site, what will the traffic manager do?

VladRomanenkoMSFT
10/27/2011 9:50:53 AM
Hi, Traffic Manager has intelligent logic to figure out where user comes from based on his local DNS resolver. The user is then sent to the closest location where Azure app has a hosted service deployed. Thus if you deploy in Asia and Europe these will be target destinations depending on network performance (latency) from your location.

bradygaster
10/12/2011 7:27:57 AM
I know Brian Hitney would be able to ask that question pretty easily, and Azure is one of the specialties with which he works on a regular basis. He's the author of the post, and is quite receptive to communication about the topic of Azure.