Route 53 Latency Based Routing

© 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.1

Latency Based Routing with Route 53

Alex Dunlap, Sr. Manager, Route 53

Nathan Dye, Software Development Manager, Route 53

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

Overview of Amazon Route 53

Overview of Latency Based Routing

Route 53 Case Studies

Demo of Latency Based Routing

Questions

Agenda

2


What is Route 53?

3

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

http://www.amazon.com/


How it Works

4

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


Design Principles

5

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 Based Routing• More to come

• Console• Programmatic API

• Inexpensive rates• Pay as you go model

• Weighted Round Robin• Self-Aliasing


Route 53’s Key Features

6

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


Latency Based Routing (LBR)

7

Run multiple stacks of your application in different EC2 regions around the world

Create LBR 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


LBR Benefits

8

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


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


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


Use Cases


foursquare

foursquare builds tools that help you keep up with friends, discover what’s nearby, save money and unlock deals.

“We wanted to eliminate the need to provision our own DNS servers. We also use ELB, and needed a solution that would let us handle DNS requests for the apex of our domain. Route 53 gave us these features, and we could use its programmatic API to automate everything into our workflow”

Robert Joseph, foursquare


Affine

Affine provides a Contextual Targeting Platform for online video advertising.

“Our customers bid on video ad inventory in real time and our system must evaluate the content they're sponsoring and respond with a decision in less than 50ms, or they'll lose the auction. Route 53’s Latency Based Routing lets us easily run multiple stacks of our whole targeting platform in each AWS region so we can meet our customers latency needs.”

Revolutionary Technology that delivers certainty to Advertisers and Agencies

Jonathan Dodson, Vice President of Engineering at Affine


Avos

In 2011, Avos systems acquired multiple domains from Yahoo associated with delicious.com, a social bookmarking site. They selected Route 53 because its management console and ELB integration made it easy to migrate these sites to AWS infrastructure.

“Route 53 made it very easy to migrate our user traffic and we were able to move all the properties to AWS on a Saturday morning. Additionally, the Route 53 console made it very easy to migrate especially with how well integrated it is with AWS’ Elastic Load Balancers”

Vijay Krunamurthy, AVOS


Academia.edu

Academia.edu is a platform for academics to share research papers.

“We run front-end servers for our site in 5 regions around the world using Latency Based Routing. Since we’ve implemented this, we’ve reduced page load times for our end users by 1-2 seconds. We also learned which servers the majority of users were near (in terms of latency) which is making us rethink our general server deployment strategy.”

Ryan Lower, Academia.edu


See more case studies at aws.amazon.com/route53

16


Demo

17


Questions?

18