|
You mentioned you have servers in different facilities, so I will mention the following since it may be useful.
Imagine you had a Linode in Fremont and a Linode in Newark both serving the same site. You could use Amazon Route 53's latency-based routing and health checks (and short TTLs) to achieve the following: Under normal circumstances, users from the Western US and Asia Pacific would be directed to your Fremont Linode, and users from the Eastern US and Europe would be directed to your Newark Linode. If either Linode went down, after about 2 minutes of failed health checks, all users would be sent to the working Linode. Once the failed Linode came back online, users would once again be automatically sent to both servers, depending on their location.
I'm not sure how else you would achieve any sort of high availability configuration across multiple datacenters without using DNS to direct users to the appropriate facilities, and this is now relatively easy to set up with Route 53.
|