{"id":69737,"date":"2019-01-22T05:50:56","date_gmt":"2019-01-22T05:50:56","guid":{"rendered":"https:\/\/www.whizlabs.com\/blog\/?p=69737"},"modified":"2021-03-15T06:25:58","modified_gmt":"2021-03-15T06:25:58","slug":"route-53-policies","status":"publish","type":"post","link":"https:\/\/www.whizlabs.com\/blog\/route-53-policies\/","title":{"rendered":"Route 53 Policies: Latency-based Routing vs Geolocation Routing"},"content":{"rendered":"

Recently one of our users has enquired about the difference between the two Route 53 policies, Route 53 Latency-based Routing policy and Route 53 Geolocation Routing Policy. It appears that both the policies will route the traffic request to the nearest resource from where the query originates. So, in that case, why do we need two different routing policies that will provide the same functionality?<\/span><\/p>\n

However, in reality, it is incorrect. These two routing policies are not just for routing the request to the nearest resource.<\/span><\/p>\n

Route 53 policies is an important topic to cover during the preparation of AWS certifications<\/a>. If you are preparing for AWS Associate Architect Certification<\/a> and AWS Certified SysOps Administrator<\/a> Associate exam, then it is a must read topic. For more details, you can go through with the complete guide of AWS Solution Architect Associate<\/a>.<\/span><\/p>\n

\n

Try Now:<\/p>\n

AWS Certified Solutions Architect Associate Free Test<\/a><\/p>\n

AWS Certified SysOps Administrator Associate Free Test<\/a><\/p>\n<\/blockquote>\n

So, let’s look into these two Route 53 policies (i.e. Route 53 Latency-based Routing policy and Route 53 Geolocation Routing Policy) with a use case scenario.<\/span><\/p>\n

Route 53 Policies: Problem Scenario<\/h2>\n

You are designing a global travel website using multi-region architecture in AWS cloud. When user\u2019s login to your website, they should have a good experience. Also, the user should be able to view the contents in the official language of the country from where the person is logging in. Due to compliance reasons, the European customer data should be stored in Europe and US customer data should be stored in the US.<\/span><\/p>\n

Which of the Route 53 policies is apt for the scenario described?<\/span><\/p>\n

Should we go for Route 53 Latency-based Routing policy or Route 53 Geolocation Routing Policy in this case?<\/span><\/em><\/p>\n

\"AWS<\/a><\/p>\n

Solution<\/h2>\n

Latency-based routing policy does ensure that the user will have a good experience in terms of latency. However, latency based routing does not always ensure that the traffic is routed to the nearest resource in terms of proximity to the source of the query.<\/span><\/p>\n

For latency-based routing, you create latency records for your resources in multiple AWS Regions. When a DNS query is received by Route 53 for your domain or sub-domain, it evaluates the latency records that you have created for AWS Regions. Then, it will determine which region provides the lowest latency to the user, and then selects the appropriate latency record for that region. <\/span><\/p>\n

However, latency will not remain same all the time. It can change as the network connectivity, traffic and routing change over time. Latency-based routing works according to the latency measurements over a period of time, and the changes are revealed in the measurements. So in this case, the latency routing policy will not work since the routing changes over time.<\/span><\/p>\n

Now let us look at the Geolocation routing. It allows Route 53 to route the traffic to the resources according to the geographic location of the source query. You can make your content localized and display your website in your own language in the Geolocation routing.<\/span><\/p>\n

\"AWS<\/a><\/p>\n

A use case for Geolocation routing:<\/strong><\/p>\n