: Way to easily host web app from multiple locations I have a web app that is latency dependant, and I would like the app to be hosted from multiple locations so that there is low latency,

@Berumen354

If you are asking if it is easy the answer is no. There are a wide range of providers out there that can do this but what you are in effect after is cloud service providers.

I will answer based on my experience in doing this.

I will need to make a few assumptions here based on your question...


You have an understanding of vertical and horizontal scaling.
You are aware of the various cloud service providers out there.
You have some level of experience in server administration, DNS management, and network management.


Step 1
The first step is to decide on a hosting provider. I can not make that recommendation to you as it depends on your unique circumstances but the bet option is to review the various cloud service providers out there and find one that meets your needs for support, costs, and service availability.

Step 2
You need to decide on the geographic regions you need to be hosting in. Based on your question I will be assuming these regions to be US-EAST, US-WEST, and EUROPE.

Step 3
Begin hosting application servers in each region behind a load balancer. How many servers you have, how they are coupled, all depends on how decoupled your application is and what backend processes it requires away from the primary application and web servers. Now you will have servers hosting your application in each region you have defined and the servers will be located behind a load balancer.

Step 4
Configure laatency based routing DNS through a DNS service provider to route your domain name configured with each load balancer in each region. At this point when you connect to the domain in your web browser you will be routed to the load balancer with the least latency to your local network.

Some Things to Consider


Distribution of code to your various servers. There are thousands of different ways this can be done, my personal preference is to use Git as a code repository and when the code is updated bring one region down at a time and set the servers up to get the latest build from the Git server when the server comes online.
This is just one way to do this and how it is done depends very much on your application, its requirements, its designs, and the logic behind how it works. If you don't have much experience with high availability application hosting and SaaS systems then I would strongly recommend you get someone with that experience to work with you on your specific project.

Vote Up Vote Down