What are the different Route 53 Routing Policies?

1. Simple
   Route traffic to a single resource. As simple as that !

2. Weighted
   Specify how much % of requests a specific resource should handle.
   Fun fact: if you specify the weight=0 for all the resources, traffic would be equally distributed.

3. Failover
   Primarily used for the DR purpose, an active-passive setup tied up with the resource health checks. If the primary health check fails, requests are auto routed to the secondary.

4. Latency based
   Redirect the users to the AWS regions with the least latency
   Fun fact: need not be the region closest to the user always!

5. Geolocation
   To route traffic based on the user location.
   Matched users are routed to the pre-configured locations, the default location is mandatory in this policy to re-direct the users from the no-match locations.

6. Multi-Value Answer
   when you want route53 to respond to DNS queries with up to 8 healthy records selected at random.
   Note: multi-value by any means is not a replacement for a load balancer.

7. Geoproximity
   Shifts traffic based on bias.
   To allow more traffic (bias range: 1 to 99)
   To shrink traffic (bias range: -1 to -99)

The diagram below shows all 7 available Route 53 Routing Policies.

Feel freel to follow me here: https://www.linkedin.com/in/govardhana-miriyala-kannaiah/

for more cool content !