Newbe Dev Stack

Answer : What web server are you using? I had a very similar issue with nginx and AWS load balancing. I added keepalive_timeout 75s; to the http block in my nginx config file and haven't see the issue since. Make sure you restart nginx after you add and save that line (on ubuntu sudo service nginx restart . On redhat stop nginx /path/to/nginx/executable -s stop then /path/to/nginx/executable to start up nginx) This fix was recommended by AWS on their help page AWS Load balancer troubleshooting First, what is the Idle Timeout for your ELB set to? You'll find it at the very bottom of the "Description" tab for your load balancer. You can read more about the idle timeout here in the ELB documentation. The default is 60 seconds. You should also consider setting or increasing Keep-alive in your web server. How you do that will depend on what web server you are using. Second, if you think it's due to the client being switched from one instance to the ot...

Answer : James, I think you already have most of it figured out. VM load balancing: Works only with VMs that are in the same region Only does Round Robin Uses a hash-based algorithm for distribution of inbound flows Works at the TCP/UDP level, routing traffic between one or more private endpoints that sit behind a public endpoint https://www.windowsazure.com/en-us/manage/windows/common-tasks/how-to-load-balance-virtual-machines/ Traffic Manager is different in that: It can work across regions It offers traffic management policies other than round robin (e.g. failover, performance) It works at the DNS level, “routing”** traffic between one or more public endpoints that sit behind a common DNS name https://azure.microsoft.com/en-us/documentation/articles/traffic-manager-manage-profiles/ You can indeed use the Load Balancer and the Traffic Manager in tandem, you hit the nail on the head there. -- Vlad ** Traffic manager does not actually route traffic, it...