Load balancer backend with failover, not just frontend!
My reason to use load balancer:
1. to split the load to multiple servers instead of single server
2. if one of the configured server is offline or temporary turn off the web service for maintenance or upgrade, there should be no interruption.
Current load balancer only supported fail over for frontend(load balancing servers itself).
Fail over for the backends(our servers) is not supported. If one of this servers is offline or the web service is not running. All website will be down. It should be like this.
-
Guest
- Oct 14 2019
Related ideas
Agree🎃! DO start working on this!
Attachments Open full size
High Availability
All DigitalOcean Load Balancers automatically monitor their backend pools and only send requests to Droplets that pass health checks. You can define health check endpoints and set the parameters around what constitutes a healthy response. The load balancer automatically removes Droplets that fail health checks from rotation, and adds them back when the health checks pass.
Redundant Load Balancer
DigitalOcean Load Balancers are configured with automatic failover to maintain availability even when failures occur at the balancing layer. Internally, the active balancing component is monitored and fails over to a standby if necessary, meaning your load balancer is never a single point of failure.
Attachments Open full size
what do you mean by backend? database server? use fail-over in the front-end application
balancer cannot health-check other servers to assume whether your app will work or not = that's called BAD programming
Attachments Open full size