Windows azure traffic manager


Published on

Faizal discussing and demonstrates Windows Azure Traffic Manager which on CTP. Traffic Manager provides several ways to load balance traffic to multiple hosted services. You can choose from three load balancing methods: Performance, Failover, or Round Robin.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 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.
  • Windows azure traffic manager

    1. 1. Windows Azure Traffic Manager<br />K.MohamedFaizal<br />Lead Consultant @ NCS (P) Ltd. <br />AzureUG.SG Meeting <br />September 27th 2011 <br /><br /><br /><br />@kmdfaizal<br />
    2. 2. About Me<br />15<br />
    3. 3. Windows Azure Traffic Manager<br />Load balancing solution.<br />Enables the distribution of incoming traffic among different hosted services in your Windows Azure subscription.<br />Regardless of their physical location. <br />Traffic routing occurs as a the result of policies that you define .<br />
    4. 4. Windows Azure Traffic Manager<br />Load balancing across multiple Hosted Services<br />Integrated in the Windows Azure Platform portal<br />Three scenarios enabled with the CTP:<br />Performance<br />Round Robin<br />Fault Tolerance<br />Redirect traffic to another deployment based on availability<br />Directs the user to the best / closest deployment<br />Traffic routed to deployments based on fixed ratio<br />
    5. 5. Windows Azure Traffic Manager (WATM) <br />Control the distribution of user traffic <br />Performance, <br />Business continuity, <br />Price, Legal or Tax purposes. <br />Compliance<br />
    6. 6. Windows Azure Platform Availability <br />Northern Europe<br />North Central USA<br />Eastern Asia<br />Western Europe <br />South Central USA<br />Southeast Asia<br />
    7. 7. How Windows Azure Traffic Manager works<br />Assign each policy a DNS name <br />Associate it with multiple hosted services. <br />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. <br />Traffic Manager constantly monitors hosted services to ensure they are online and will not route traffic to any service that is unavailable. <br />
    8. 8. 1<br />2<br />3<br />
    9. 9. How Windows Azure Traffic Manager Works<br />Traffic Manager Policy<br />Traffic Manager Domain<br /><br />Load Balance Method<br />Monitoring<br />East Asia <br />World Apps<br />West Europe <br />World Apps<br />South Central<br />World Apps<br />Windows Azure Hosted Services<br />
    10. 10. Performance<br />Performance Times Table built periodically<br />Incoming request <br />Performance table lookup <br />Best performing service chosen <br />DNS name returned <br />Service call<br />
    11. 11. Hosted Application on Following Data Center<br />East Asia<br />West Europe <br />South Central US<br />
    12. 12. Windows Azure Traffic Manager - Performance<br />Northern Europe<br />North Central USA<br />Eastern Asia<br />Western Europe <br />South Central USA<br />Southeast Asia<br />4<br />6<br />3<br />1<br />Closest?<br />2<br />5<br />
    13. 13. Performance - Demo<br />
    14. 14. Windows Azure Traffic Manager - Round Robin<br />Northern Europe<br />North Central USA<br />Eastern Asia<br />Western Europe <br />6<br />South Central USA<br />Southeast Asia<br />5<br />Next ?<br />Last = West Europe<br />2<br />Last = Eastern Asia<br />4<br />1<br />3<br />
    15. 15. Round Robin - Demo<br />
    16. 16. Windows Azure Traffic Manager - Failover<br />Northern Europe<br />North Central USA<br />Based your policy the traffic is sent to the next in order<br />Eastern Asia<br />Western Europe <br />South Central USA<br />2<br />Southeast Asia<br />4<br />Your Application Offline @ US Central Data Center<br />Online <br />Hosted Service<br />1<br />3<br />
    17. 17. Failover - Demo<br />
    18. 18. Monitoring Hosted Services <br />
    19. 19. Best Practices<br />Services should be in a single subscription <br />Production services only <br />Name your hosted services so they can be easily found and clustered into policies <br />All services in a policy should service the same operations and ports<br />All services in a policy must use the same monitoring method <br />
    20. 20. Others<br />Custom domain name <br />No automatic deployment <br />What about Data? <br />
    21. 21. Questions & Answers<br />21<br />