The Windows Azure Traffic Manager CTP was announced at Mix 2011. Windows Azure Platform Training Kit (April 2011) included the hands-on lab for Traffic Manager.
For September AzureUG.SG meeting i share what is Windows Azure Traffic Manager and how does helps organization to run worldwide enterprise applications.
Windows Azure Traffic Manager helps to distributing the same internet application that hosted on various Azure datacentre in worldwide. The Traffic Manager provide following options to distribute the DNS Service and Request by managing the URL.
- Performance : Traffic is routed to “Closest” hosted service in terms of network latency
- Failover : Traffic is routed to primary service, In case of primary service down, the traffic route to next available datacentre.
- Round-robin: traffic distributed requests between azure datacentres.
Windows Azure Traffic Manager Key Features
Host Worldwide Enterprise Application in to various Azure Datacentres
For this demo i hosted application in to following azure datacentres.
- East Asia
- West Europe
- South US Central
Configure Windows Azure Traffic Manager via Windows Azure Management Portal. The windows azure Traffic manager is currently on CTP so go beta program and request for access. (usually Microsoft approve your request every Wednesday) so you may need wait to activate this service.
Once your requested activated, Go Windows Azure Management Portal, select the Virtual Network tab. Then, choose the Policies option under Traffic Manager and click Create.
Windows Azure Traffic Manager Policy Settings
The numbered steps below correspond to the numbers on the diagram.
1. Performance Times Table built periodically - The traffic manager infrastructure runs tests to determine the round trip times between different points in the world and the Windows Azure data centres which run hosted services. These tests are run at the discretion of the Windows Azure system.
2. Incoming request - Your Traffic Manager domain receives an incoming request from a client machine.
3. Performance table lookup - Traffic Manager looks up the round trip time between the location of the incoming request and the hosted services that are part of your policy using the table created in step 1.
4. Best performing service chosen - Traffic Manager determines the location of the hosted service with the best time. In this example, that is HS-D.
5. DNS name returned - Traffic manager returns the DNS name of hosted service D to the client machine.
6. Service call - The client machine resolves the DNS name to the IP address and calls the hosted service.
The numbered steps below correspond to the numbers on the diagram.
1. Your Traffic Manager domain receives an incoming request from a client.
2. Your policy contains an ordered list of hosted services. Traffic manager knows which service received the last request.
3. Traffic Manager sends the DNS entry pointing to the next hosted service in the list back to the client. In this example, this is hosted service East Asia
4. Traffic Manager updates itself to so it knows that the last traffic went to hosted service East Asia .
5. The client machine uses the DNS entry and calls hosted service East Asia.
6. The client machine uses the DNS entry and calls hosted service South Central US.
The numbered steps below correspond to the numbers on the diagram.
1. Your Traffic Manager domain receives an incoming request from a client.
2. Your policy contains an ordered list of hosted services. Traffic Manager checks which hosted service is first in the list. It verifies that the hosted service is online. If the hosted service is offline, it proceeds to the next online hosted service. In this case South Central USA is offline, but Eastern Asia is online.
3. Traffic Manager returns the DNS entry to the client. The DNS entry points to the IP address of Eastern Asia.
4. The client machine calls Eastern Asia.
No comments:
Post a Comment