Load balancing

How to achieve zero downtime deployment?

Most websites need to be up 24 hours every day, so we need a solution to deploy changes to the website without taking it down. The solution is to have more than one application server and use a load balancer. You have your application running on one of the servers and when you need to make changes, you deploy the new version on the other server. Now when a user is currently using the website he will still be using the old version, but when he connects to the website the next time he will be redirected to the other server with the new version. As long as there are sessions on the old version it keeps running, and when all the sessions are on the new server you can take down the old version and keep that server free for the next time you need to deploy changes.

Network Optimization - Load sharing between ISPs or one ISP as main and other ISP as backup link

Network Optimization - Internet Speed and cost is really important now days. When two internet service providers is providing different kind of service. Like if we have one Internet Service Provider is A1 who is expensive but Service is good and downtime is less and other service provider is UPS who´s solution is cheapest but downtime is higher than we have find one solution for our organization to combine both the Service and then we will need Load balance internet traffic. I'm interested in load balancing internet traffic (outbound -AND- INBOUND) using multiple (at least 2) ISPs. Some of the methods I have used in the past have certain weaknesses.. basic DNS load balancer (relies on multiple IP addresses per host), OER/PFR (ability to control INbound is limited unless complex configuration and cooperation with ISPs)...
Subscribe to Load balancing