A load balancer distributes traffic across a backend pool of servers to improve the stability and responsiveness of an application.
By using a load balancer, the servers are less likely to overload. Load balancers sit between the user devices and servers, and receive and distribute incoming requests to available servers.
In App Platform, a load balancer is the part of your app’s infrastructure that handles incoming requests. Load balancing is a built-in part of how App Platform works, meaning you don’t need enable or configure it.
Load balancers have two primary functions:
Distributing incoming requests evenly across all containers that pass a health check and provide capacity to your service. Distributing requests this way is what enables your service’s high availability.
Routing incoming requests from the HTTP and HTTPS ports (80 and 443, respectively) to an internal port that App Platform calls the HTTP Port (8080 by default).
You can use load balancers to distribute Docker containers across a cluster of servers, with all of the containers accessible by the same host port.
DigitalOcean does not support automatic creation of Let’s Encrypt certificates for DigitalOcean Load Balancers. Instead, you must generate certificates yourself.
For more information about the limits, see Load Balancers Limits.
In App Platform, a load balancer handles incoming requests. Load balancing is a built-in part of how App Platform works, meaning you don’t need enable or configure it.
DigitalOcean Load Balancers ensure that the requests your application receives are only distributed to Droplets that have passed health checks. Load balancers remove Droplets from rotation that have failed health checks, and only add them back when they have passed health checks. Using load balancers is an important component to making your service or application highly available.