A company currently hosts its architecture in the US region.
They now need to duplicate that architecture to the European region and extend the application hosted on this architecture to the new region.
In order to ensure that users across the globe get the same seamless experience from either setup, what needs to be done?
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - D.
The AWS Documentation mentions the following to support this requirement.
Geolocation routing lets you choose the resources that serve your traffic based on the geographic location of your users, meaning the location that DNS queries originate from.
For more information on AWS Route53 Routing policies, please visit the following URL:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.htmlTo ensure that users across the globe get the same seamless experience from either setup, the company needs to set up a global infrastructure that can route user requests to the nearest endpoint.
Option A: Create a classic Elastic Load Balancer that is set up to route traffic to both locations. This option is not recommended because Classic Load Balancers do not support cross-region load balancing. Therefore, this option would not work as expected.
Option B: Create a weighted Route53 policy to route the policy based on the weightage for each location. This option is feasible. Route53 is a global DNS service provided by AWS that can distribute traffic across multiple regions based on configurable routing policies. With the weighted policy, you can distribute traffic between regions based on a set of weights that you define. You can allocate more weight to the region closer to the user to ensure that requests are served from the nearest endpoint.
Option C: Create an Application Elastic Load Balancer that is set up to route traffic to both locations. This option is feasible. An Application Load Balancer (ALB) is a Layer 7 load balancer that can route traffic based on content and application-specific parameters. ALBs support cross-region load balancing, and you can create a target group for each region and distribute traffic based on the health of the target group.
Option D: Create a geolocation Route53 policy to route the policy based on the location. This option is also feasible. A geolocation policy enables you to route traffic based on the geographic location of the user. You can create multiple records in Route53, each with a different IP address for each region. When a user requests a domain name, Route53 will check the location of the user and route the request to the IP address that is closest to the user.
Therefore, options B, C, and D are feasible solutions for the company's requirement. However, the best solution depends on the specific requirements of the company, such as the application architecture, performance requirements, and budget constraints.