Downloaded 35 times
Uploaded byK.Mohamed Faizal
Windows azure traffic manager
The document discusses the Windows Azure Traffic Manager, a load balancing solution that distributes incoming traffic among various hosted services in Azure regardless of their location, using defined policies. It highlights three routing scenarios: performance, round robin, and fault tolerance, while also addressing compliance and monitoring methods for service availability. Best practices for service configuration and management within Azure Traffic Manager are also outlined.
More Related Content
![[Webinar] AWS Monitoring with Site24x7](https://cdn.slidesharecdn.com/ss_thumbnails/site24x7-awsmonitoringwithsite24x704thnov2015-151105060402-lva1-app6891-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Windows azure traffic manager
More from K.Mohamed Faizal
Windows azure traffic manager
- 1. Windows Azure TrafficManagerK.MohamedFaizalLead Consultant @ NCS (P) Ltd. AzureUG.SG Meeting September 27th 2011 http://faizal-comeacross.blogspot.com/kmdfaizal@yahoo.comhttp://www.facebook.com/kmdfaizal@kmdfaizal
- 2.
- 3. Windows Azure TrafficManagerLoad balancing solution.Enables the distribution of incoming traffic among different hosted services in your Windows Azure subscription.Regardless of their physical location. Traffic routing occurs as a the result of policies that you define .
- 4. Windows Azure TrafficManagerLoad balancing across multiple Hosted ServicesIntegrated in the Windows Azure Platform portalThree scenarios enabled with the CTP:PerformanceRound RobinFault ToleranceRedirect traffic to another deployment based on availabilityDirects the user to the best / closest deploymentTraffic routed to deployments based on fixed ratio
- 5. Windows Azure TrafficManager (WATM) Control the distribution of user traffic Performance, Business continuity, Price, Legal or Tax purposes. Compliance
- 6. Windows Azure PlatformAvailability Northern EuropeNorth Central USAEastern AsiaWestern Europe South Central USASoutheast Asia
- 7. How Windows AzureTraffic Manager worksAssign each policy a DNS name Associate it with multiple hosted services. The load balancer responds to queries for the policy DNS name with the address of one of the associated hosted services that satisfies the criteria for the policy. Traffic Manager constantly monitors hosted services to ensure they are online and will not route traffic to any service that is unavailable.
- 8.
- 9. How Windows AzureTraffic Manager WorksTraffic Manager PolicyTraffic Manager DomainPerformance.worldapps.ctp.trafficmgr.comLoad Balance MethodMonitoringEast Asia World AppsWest Europe World AppsSouth CentralWorld AppsWindows Azure Hosted Services
- 10. PerformancePerformance Times Tablebuilt periodicallyIncoming request Performance table lookup Best performing service chosen DNS name returned Service call
- 11. Hosted Application onFollowing Data CenterEast AsiaWest Europe South Central US
- 12. Windows Azure TrafficManager - PerformanceNorthern EuropeNorth Central USAEastern AsiaWestern Europe South Central USASoutheast Asia4631Closest?25
- 13.
- 14. Windows Azure TrafficManager - Round RobinNorthern EuropeNorth Central USAEastern AsiaWestern Europe 6South Central USASoutheast Asia5Next ?Last = West Europe2Last = Eastern Asia413
- 15. Round Robin -Demo
- 16. Windows Azure TrafficManager - FailoverNorthern EuropeNorth Central USABased your policy the traffic is sent to the next in orderEastern AsiaWestern Europe South Central USA2Southeast Asia4Your Application Offline @ US Central Data CenterOnline Hosted Service13
- 17.
- 18.
- 19. Best PracticesServices shouldbe in a single subscription Production services only Name your hosted services so they can be easily found and clustered into policies All services in a policy should service the same operations and portsAll services in a policy must use the same monitoring method
- 20. OthersCustom domain nameNo automatic deployment What about Data?
- 21.
Editor's Notes
- #19 The numbers in the diagram correspond to the numbered explanation below it.GET - The Traffic Manager monitoring system performs a GET on the file you specify in the relative path area. 200 OK - The monitoring system expects a 200 OK message back within 5 seconds. When it receives this response, it assumes that the hosted service is online. 30 Seconds between checks - It will perform this check every 30 seconds. Hosted service offline - The hosted service goes offline. Traffic Manager will not know until the next monitor check.3 Tries to access monitoring file - The monitoring system performs a GET, but does not receive a response in 5 seconds or less. It performs two more tries at 30 second intervals. This means that at most it takes 1.5 minutes for the monitoring system to detect when a service goes down. If one of the tries is successful, then the number of tries is reset. Although not shown in the diagram, if the 200 OK response(s) come back greater than 5 seconds after the GET, the monitoring system will still count this as a failed check.Marked Offline - After the third failure in a row, the monitoring system will mark the hosted service as offline. Traffic to hosted service decreases – Traffic may continue to flow to the offline hosted service. Clients will experience failures because the hosted service is down. Clients and secondary DNS servers have cached the DNS address of the offline hosted service. They continue to resolve the DNS name of the company domain to the IP address of the hosted service. As DNS servers are updated, traffic to the offline hosted service IP address will stop. The monitoring system continues to perform checks at 30 second intervals and in this example the hosted service does not respond. It remains offline.Traffic to hosted service stops – By this time, most DNS servers and clients should be updated and traffic to the offline hosted service will stop. The maximum amount time before traffic completely stops is dependent on the TTL time. The default DNS TTL is 300 seconds (5 minutes). Using this value, clients stop using the service after 5 minutes. The monitoring system continues to perform checks at 30 second intervals and the hosted service does not respond.Hosted service comes back online – The hosted service comes back online, but Traffic Manager does not know until the monitoring system performs a check.Hosted service receives traffic again - Traffic Manager sends a GET and receives a 200 OK in under 5 seconds. It begins to hand out the hosted services DNS name DNS servers as they request updates. As a result, traffic starts to flow to the hosted service once again.