Amitz
New Member
Dear all,
I would like to install something that I would call "Poor man's load balancing / geo-based forwarding" and would appreciate your hints.
Here is the idea:
I have a site that has an equal amount of visitors from the EU and America (The continent, not the country). I would like to run 2 VPS with the actual website content. One in the USA (Server A), one in the EU (Server B )
Sync between the two is already up an running, so this is not an issue.
Furthermore, there will be Server C. This server will be a small VPS or cloud instance at Prometeus/iwStack because of the impressive uptime that I have seen with them throughout the last 2 years. Server C will be the A-Entry of the domain in question. In my wildest dreams, Server C will look where the visitor comes from and either forwards him to Server A or Server B, based on the geo-location of the visitor. If Server C cannot geo-locate the visitor, then it will at least try to forward the requests equally to both other servers. All this should happen (if possible) non-transparent to the visitor, meaning that there will be no change in the URL, like us.domain.com or eu.domain.com.
Has anyone of you ever setup something like this and - if yes - would be willing to give me some insight? I am not looking (even though this would surely be nice) for a complete guide. I am willing to read and to learn. So any hint in the right direction is helpful.
Thank you for taking the time & kind regards
Amitz
P.S.: I forgot to mention - I would like to do this without having to pay for out-of-the-box solutions.
Could HAProxy be my solution?
https://www.digitalocean.com/community/articles/how-to-use-haproxy-to-set-up-http-load-balancing-on-an-ubuntu-vps
I would like to install something that I would call "Poor man's load balancing / geo-based forwarding" and would appreciate your hints.
Here is the idea:
I have a site that has an equal amount of visitors from the EU and America (The continent, not the country). I would like to run 2 VPS with the actual website content. One in the USA (Server A), one in the EU (Server B )
Sync between the two is already up an running, so this is not an issue.
Furthermore, there will be Server C. This server will be a small VPS or cloud instance at Prometeus/iwStack because of the impressive uptime that I have seen with them throughout the last 2 years. Server C will be the A-Entry of the domain in question. In my wildest dreams, Server C will look where the visitor comes from and either forwards him to Server A or Server B, based on the geo-location of the visitor. If Server C cannot geo-locate the visitor, then it will at least try to forward the requests equally to both other servers. All this should happen (if possible) non-transparent to the visitor, meaning that there will be no change in the URL, like us.domain.com or eu.domain.com.
Has anyone of you ever setup something like this and - if yes - would be willing to give me some insight? I am not looking (even though this would surely be nice) for a complete guide. I am willing to read and to learn. So any hint in the right direction is helpful.
Thank you for taking the time & kind regards
Amitz
P.S.: I forgot to mention - I would like to do this without having to pay for out-of-the-box solutions.
Could HAProxy be my solution?
https://www.digitalocean.com/community/articles/how-to-use-haproxy-to-set-up-http-load-balancing-on-an-ubuntu-vps
Last edited by a moderator: