Reputation: 83
They seem pretty similar to me. Both divide traffic based on weights configuration(Weighted - weight, Geoproximity - bias).
Upvotes: 1
Views: 1250
Reputation: 8140
For Geoproximity, AWS will route the traffic based on your user and your resource locations.
Geoproximity routing lets Amazon Route 53 route traffic to your resources based on the geographic location of your users and your resources. You can also optionally choose to route more traffic or less to a given resource by specifying a value, known as a bias. A bias expands or shrinks the size of the geographic region from which traffic is routed to a resource.
If you have two locations set up, this means that if 90% of your users come from (or are near) location A, your traffic will flow to location A aswel.
While for weighted:
Weighted routing lets you associate multiple resources with a single domain name (example.com) or subdomain name (acme.example.com) and choose how much traffic is routed to each resource. This can be useful for a variety of purposes, including load balancing and testing new versions of software.
This means that for weighted you will specify how much traffic should flow to which target. This could be done for loadbalancing for example. This does mean that for weighted users close to location A might end up on servers in location B
More information can be found on the development guide
Upvotes: 1
Reputation: 270224
From Choosing a routing policy - Amazon Route 53:
Examples:
Upvotes: 2