I am looking for a latency (or geo) load balancing solution combined with dynamic fail overing.
The infrastructure is based on 3 dedicated severs from OVH. The servers are located in 3 different geographical locations (Canada, France and Australia).
There are few things I am trying to achieve:
- Client accessing the service are redirected to the closest server, so the response is quick.
- If one server is out of service the request will go to the other server and eventually user will get the response.
- In failover conditions it is more important that the user get the answer rather the it will be quick response.
- I need to have the possibility to restart the server to upgrade or something once in a while. So the magic has to be outside of the main servers.
- The traffic goes through HTTPS, but HTTP shall redirect to HTTPS.
I am interested only in HTTP traffic. Each request has to go to the server, nothing can be cached as the response is very dynamic.
I have already looked at AWS Route 53, which is great but it is just a DNS, so it will not solve the failovering part.
OVH has IP load balancing, but I cannot make it to work and I did't found option to solve problem 1.
I am interested in any hint or solution including the usage of third party services.
I am also considering an option to buy 3 small VPS servers in each location (close to the each one of main servers) which will act as a gateway. In such solution I can use AWS Route 53 to provide latency load balancing to the VPS servers and the servers will handle failovering. By the definition they will be active 100% of the time, while the main servers will have a change to restart without downtime of the service.