Your SlideShare is downloading. ×
0
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Routing in the cloud
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Routing in the cloud

403

Published on

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 …

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

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
403
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 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.
  • Transcript

    • 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
    • 3. Agenda • DNS • Routing Types • Azure Traffic Manager • Amazon Route 53 • References • Q & A
    • 4. Why need Routing? • High Availability • Low latency • High Performance
    • 5. Domain Naming System • What is DNS? • DNS Record Types • A or AAAA • NS • CNAME • MX • SOA
    • 6. Routing Types • Simple • Round Robin • Weighted • Performance or Latency • Failover
    • 7. • •
    • 8. www-contoso.trafficmgr.com www.contoso.com www.contoso.com A: 11.22.33.44
    • 9.
    • 10. Traffic Manager Demo
    • 11. © 2011 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified or distributed in whole or in part without the express consent of Amazon.com, Inc. What is Route 53? Route 53 is AWS’s authoritative Domain Name (DNS) service DNS translates domain names (like www.amazon.com) into IP addresses – think of it as a “phone book” for the internet DNS is a Tier-0 service – availability is most important We chose the name “Route 53″ as a play on the fact that DNS servers respond to queries on port 53
    • 12. © 2011 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified or distributed in whole or in part without the express consent of Amazon.com, Inc. How it Works Users DNS Resolver Route 53 Where is www.example.com? I don’t know – I’ll ask the authority 1.2.3.4 1.2.3.4 53
    • 13. © 2011 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified or distributed in whole or in part without the express consent of Amazon.com, Inc. Design Principles Reliable Fast Integrated with AWS Easy to Use Cost Effective Flexible • Redundant locations • Backed with SLA • Worldwide anycast network • Fast propagation of changes • ELB-Alias Queries • Latency/Performance Based Routing • Weighted • Failover • Console • Programmatic API • Inexpensive rates • Pay as you go model • Weighted Round Robin • Self-Aliasing
    • 14. © 2011 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified or distributed in whole or in part without the express consent of Amazon.com, Inc. Route 53’s Key Features High Availability DNS • Highly available and scalable DNS service. • Map the root or apex of your hosted zone to your Elastic Load Balancer. • Run applications in multiple AWS regions and route users to the one that provides the lowest latency. • Specify the frequency with which different responses are served. Alias Records Weighted Round Robin Latency Based Routing
    • 15. © 2011 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified or distributed in whole or in part without the express consent of Amazon.com, Inc. Latency Based Routing (LBR) Run multiple stacks of your application in different EC2 regions around the world Create Routing records using the Route 53 API or Console • Tag each destination end-point to the EC2 region that it’s in • End-points can either be EC2 instances, Elastic IPs or ELBs Route 53 will route end users to the end-point that provides the lowest latency
    • 16. © 2011 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified or distributed in whole or in part without the express consent of Amazon.com, Inc. LBR Benefits Better performance than running in a single region Improved reliability relative to running in a single region Easier implementation than traditional DNS solutions Much lower prices than traditional DNS solutions
    • 17. © 2011 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified or distributed in whole or in part without the express consent of Amazon.com, Inc. Pay-as-you-go Pricing Hosted Zones • $0.50 per hosted zone / month for the first 25 hosted zones • $0.10 per hosted zone / month for additional hosted zones Standard Queries • $0.500 per million queries – first 1 Billion queries / month • $0.250 per million queries – over 1 Billion queries / month Latency Based Routing Queries • $0.750 per million queries – first 1 Billion queries / month $0.375 per million queries – over 1 Billion queries / month Alias queries for ELBs free of charge
    • 18. © 2011 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified or distributed in whole or in part without the express consent of Amazon.com, Inc. Getting Started with LBR Sign up: aws.amazon.com/route53 Create a Hosted Zone Create your DNS records, including LBR Records Update your domain registrar with Route 53 name servers
    • 19. 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
    • 20. Route 53 Demo
    • 21. References • http://msdn.microsoft.com/en- us/library/windowsazure/hh744833.aspx • http://www.slideshare.net/windowsazure/windows-azure-traffic- manager-overview • http://www.slideshare.net/AmazonWebServices/route-53-latency- based-routing • http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/Welco me.html • http://en.wikipedia.org/wiki/Resolver_(DNS)#DNS_resolvers • http://technet.microsoft.com/en-us/library/dd197515(v=WS.10).aspx
    • 22. Question?
    • 23. Thank you for attending Boston Azure Cloud Usergroup

    ×