Everyone, and welcome back now into this, we will be discussing about routing policies in drought
53, no doubt policy basically determines how your Amazon drought 53 responds to the Kuwaitis.
Now, there are a lot of routing policies that are available in drought 53.
And depending upon the use case, you can select one among them.
Now, we'll be understanding this in more detail, but just at a high level where we just know that
there are multiple voting policies like simple way you have latency feel or geolocation as well as multibillions.
Now, before we go ahead and discuss about this in more detail, let me quickly show you on where do
you exactly select the routing policy now?
Once you have a hosting zone in Route 53, when you go ahead and create a record while creating the
record and the routing policy, you see that there are multiple routing policies that can be used.
And it is important for us to understand at a high level overview what exactly these routing policies
are all about.
Now, the first and the simplest among them is a simple routing policy where you have a plane, one
to one mapping between that domain and the host.
So, for example, you have a record number of blogger Kiplagat Internet, which has its associated
value.
So this is a very simple routing, policy based example.
Now, the second important one is the failure routing.
So failure routing lets you roll the traffic to a resource vendor, resouces Hildy or to a different
resource vendor for resources ANELI, for example, if Froud 53 routing the traffic to this specific
easy to instance, this is perfectly fine.
But what happens if this AC2 instance goes down then with the help of fellow routing at all, 53 can
go ahead and send the traffic to a different resource altogether.
So this is what Filho routing refers to.
So if what resource fears about 53 will have intelligence to understand the failure and automatically
round the traffic to a different end point itself.
Now, the next important type of routing policy is Collazo weighted routing policy.
No weighted routing policy basically allows us to allow the traffic to multiple resources in a proportion
that we specify from Oranje.
So you have about 53.
And let's say that there are two easy two instances and you have specified 50 50 Horia.
So that basically means 50 percent of the traffic will go to see Duvan and 50 percent of the traffic
will go to easy to do.
Now, depending upon the configuration, you can send 10 percent of the traffic to exceed the one and
90 percent of traffic.
Too easy to do.
So depending upon the way that you add the routing would differ accordingly.
So that's what we did.
The routing is all about that.
Next is the latency based routing.
So if your application is primarily hosted in multiple AWG region, then you can improve the performance
for users by serving the request from the database region that provides the lowest latency.
So you have multiple servers across the region.
Now, it can happen that the first AC2 instance has a higher latency and the second NICITA instance,
which is in a different part of the world, has a lower latency.
So latency based routing.
The traffic is directed towards the server, which has the lowest latency.
Now the last one for today's video is geolocation routing, which basically allows us to choose different
resources for different user based on different countries or continents.
For example, if there are two users from India and USA based upon the geolocation routing rules, about
53, you automatically routing traffic to different resources.
So, for example, India user, when he visits around 53 about doubt, he will direct them to the U.S.
to instanced, which is based on the Singapore region.
If an individual from the US he sends a query to around 53, around 50, he may redirect him to the
instance that is based on the Oregon region.
That's great.
So I hope at a very high level or you understood about the basics, about the routing policies that
are part of aroud 53 so that this will conclude today's.
We do.