Load balancing
Concepts
A load balancer is responsible for distributing the workload among upstreams for either dedicated or cloud servers.
Getting started
To create a load balancer, you need at least one provisioned server.
Limitations
The balancer has the following limitations:
Billing
The service is provided on a postpaid basis. Your account will be charged at the end of the month according to the actual usage.
How-tos
How to add or remove an upstream in an existing load balancer, How to delete the load balancer
Features specific to HTTP(S) load balancing
You need to specify at least one domain name to set up a load balancer instance in HTTP(S) (Layer 7) mode. The load balancer only processes requests to the configured domain names. HTTP/HTTPS requests with no domain name specified are dropped and the connection is closed.
Considerations on using multiple domain names with a single instance
You can add multiple domain names when creating a load balancer instance. At the same time, you will be able to add only one SSL certificate for the instance. This certificate will be used to respond to all request to that instance. Thus to protect multiple domain names you will need a wildcard certificate in case the domains are subdomains of the same 2nd level domain, or you will need a SSL certificate with SAN extension for multiple domains.
Access Logs
The "Logs storing" feature allows for logging information about requests processed by a load balancer to NGINX-style access log files. Logs are available in minute-long segments placed in the cloud storage of your Servers.com account. New files are added in batches of five every five minutes.
