Routing in the cloud

28
Routing in the Cloud Azure Traffic Manager and Amazon Route 53 Udaiappa Ramachandran ( Udai ) @nhcloud

description

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

Transcript of Routing in the cloud

Page 1: Routing in the cloud

Routing in the CloudAzure Traffic Manager and Amazon Route

53

Udaiappa Ramachandran ( Udai )@nhcloud

Page 2: Routing in the cloud

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

Page 3: Routing in the cloud

Agenda

• DNS• Routing Types• Azure Traffic Manager• Amazon Route 53• References• Q & A

Page 4: Routing in the cloud

Why need Routing?

• High Availability• Low latency• High Performance

Page 5: Routing in the cloud

Domain Naming System

• What is DNS?• DNS Record Types

• A or AAAA• NS• CNAME• MX• SOA

Page 6: Routing in the cloud

Routing Types

• Simple• Round Robin• Weighted• Performance or Latency• Failover

Page 7: Routing in the cloud

Load balance incoming traffic across multiple hosted Windows Azure services to provide your applications high performance, availability and resiliency.

Windows Azure Traffic Manager

Page 8: Routing in the cloud

Windows Azure Traffic ManagerDNS (Domain Name System) based load balancing of hosted services

Direct user traffic to services running across Windows Azure datacenters based on routing policies

Provide health monitoring to your services

Performance

Direct traffic to “closest” service based on network latency

Round-robin

Distribute traffic equally across all services

FailoverDirect traffic to “backup” service if primary service fails

www.foo.com

foo.trafficmanager.net• Load-balancing• Service health monitoring

HostedServiceHostedServiceHostedService

HostedService

Page 9: Routing in the cloud

“choose the best performing deployment” between:

Deployment ADeployment BDeployment C

DNS Server

Q: What is www-contoso.trafficmgr.com?

Policy Engine

Traffic Manage

r

5

www-contoso policy

How Traffic Manager Works

Deployment AUS North

Deployment BWest Europe

Deployment C (Down)

IP=11.22.33.44 IP=22.33.44.55IP=33.44.55.66

20ms 80ms

ns1.contoso.comns2.contoso.com

Q: What is www.contoso.com?

A: CNAME to www-contoso.trafficmgr.com

34

6

7

8

Which deployments are up?

What are the regions for deployments A and B?

What is the network distance between IP 99.88.77.66 and the US North and West Europe regions?

Users’ LDNSIP=99.88.77.6

6

a.root-servers.net…

k.root-servers.net

Q: What is www.contoso.com?A: Ask ns1/2.contoso.com

12

9A: 11.22.33.44

Page 10: Routing in the cloud

Traffic Manager Benefits

Simplifies the task of building highly-reliable and scalable applications by setting up routing policies within minutes

Quick setup

Faster page load and better end-user experience by serving users with the hosted service that is “closest” to them

Performance

Monitor critical applications and providing automatic failover capabilities when a service goes down

Availability

Page 11: Routing in the cloud

Traffic Manager Scenarios

Build high performing cloud applications

Planning for disaster recovery

Upgrade Cloud Applications seamlessly

Page 12: Routing in the cloud

Improving PerformanceNorth America Region Europe Region Asia Pacific Region

www.contoso.com

30ms 130ms

240ms

www.contoso.com www-contoso.trafficmanager.net

30ms 20ms40ms

Page 13: Routing in the cloud

Disaster RecoveryNorth America Region Europe Region Asia Pacific Region

30ms 20ms40ms

Service health monitoring

120ms

Page 14: Routing in the cloud

Upgrading Windows Azure Application

Subscription

Region A – US North Region B – East Asia

Role 1 Role 1

api-contoso.trafficmanager.net

api.contoso.com

CNAME

api2.cloudapp.netapi.cloudapp.net

Upgraded Role 1

Test application

Page 15: Routing in the cloud

Traffic Manager Demo

Page 16: Routing in the cloud

© 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

Page 17: Routing in the cloud

© 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

Page 18: Routing in the cloud

© 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

Page 19: Routing in the cloud

© 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

Page 20: Routing in the cloud

© 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

Page 21: Routing in the cloud

© 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 BenefitsBetter 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

Page 22: Routing in the cloud

© 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

Page 23: Routing in the cloud

© 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

Page 24: Routing in the cloud

Comparison

Traffic Manager Route53Simple, Round-robin, performance and failover Simple, weighted, round-robin, performance and

failoverDomain Naming system DNS with Authorative (SOA)REST Endpoint REST and SDKFor now it supports Hosted Services (PaaS) PaaS and IaaS supportStateless required Cookie based stickinessCNAME Record Type All types of Record Type

Page 25: Routing in the cloud

Route 53 Demo

Page 26: Routing in the cloud

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/Welcome.html

• http://en.wikipedia.org/wiki/Resolver_(DNS)#DNS_resolvers• http://technet.microsoft.com/en-us/library/dd197515(v=WS.10).aspx

Page 27: Routing in the cloud

Question?

Page 28: Routing in the cloud

Thank you for attending Boston Azure Cloud Usergroup