On September 26, I had the privilege of speaking at the Boston Azure User Group in Boston, MA. The topic covered a in-depth discussion of DNS Routing in Microsoft Azure Traffic Manager and Amazon Route53. It was an very interactive session with lots of great questions from the attendees. The topics that we covered
1. Routing in the Cloud
Azure Traffic Manager and Amazon Route 53
Udaiappa Ramachandran ( Udai )
@nhcloud
2. Who am I?
• Udaiappa Ramachandran ( Udai )
• Chief Architect, Ektron, Inc.,
• Azure Insider
• New Hampshire Cloud User Group (http://www.nashuaug.org )
• Focus on Cloud Computing
• Windows Azure and Amazon Web Services
• http://cloudycode.wordpress.com
• @nhcloud
24. Comparison
Traffic Manager Route53
Simple, Round-robin, performance and failover Simple, weighted, round-robin, performance and
failover
Domain Naming system DNS with Authorative (SOA)
REST Endpoint REST and SDK
For now it supports Hosted Services (PaaS) PaaS and IaaS support
Stateless required Cookie based stickiness
CNAME Record Type All types of Record Type
28. Thank you for attending
Boston Azure Cloud
Usergroup
Notas del editor
Set the context…
Performance Policy Example: Building a Geo-Distributed service. If you have users using your service around the globe, deploy your hosted service into multiple regions (i.e. US, Europe, Asia) and have your users routed to the nearest location.Failover Policy Example: Having a “hot” standby service. If the primary service is offline, requests will be routed to the next in order, and so on.Round Robin Example: Increased scalability and availability within a region. Spread the load across multiple services with multiple instances. Note that Traffic Manager still monitors health and will not route a request to a service that is down.Using Traffic Manager for MonitoringInstead of adding third-party URL based monitoring to a web site hosted in Windows Azure, you can now leverage the monitoring capabilities provided by Traffic Manager to do the same thing.