DigitalOcean load balancers provide a way to distribute requests for the same domain to multiple servers. For DigitalOcean load balancers to be useful to you, you must have the exact same app running on multiple servers.
DigitalOcean load balancers can be used when you have multiple backend app servers running the exact same app. Using a load balancer in this situation allows you to handle more traffic than even a single, extremely large server could handle and also provides for redundancy in case one of your app servers goes down.
Using a load balancer increases the complexity of your server and app configuration as it requires using a separate database server, keeping all of your app servers running the same version of your code, configuring the load balancer, and customizing your servers to understand the load balancer's IP address is not the client address; all of this can make SSL configuration much more complicated and error-prone. If you aren't familiar with how to manage this complexity, you risk downtime and security problems by using a load balancer.
If you are not an experienced sysadmin, you should not use DigitalOcean load balancers.
Even if you are an experienced sysadmin, you should be aware of a few limitations of DigitalOcean load balancers:
When you're ready to get started with DigitalOcean load balancers, first configure your backend app servers.
Then, decide which type of DigitalOcean load balancer to use and carefully read the DigitalOcean documentation on how to create that type of load balancer: