24/7 Non-stop, Stable Service
A load balancer distributes network traffic to multiple servers to relieve loads on servers. When one of the servers connected to the load balancer fails, the load on the server is automatically distributed to other servers, to ensure a highly stable service.
- High Availability
- If one of the servers connected to the load balancer fails, the load on the server is automatically distributed to the other servers for uninterrupted service. In addition, a server connected to one load balancer can be multi-connected to another load balancer.
- Easy Setting
- On the web-based console, you can create and manage the settings of load balancers easily. The monitoring features are also supported. A RESTful API for developers can be used for easy setup.
- Encryption-based Security
- Supports encrypted communication, such as TLS v1.0, TLS v1.1, TLS v1.2 to respond to security problems that may arise during the course of your network. In addition, the SSL offloading function enables decryption processing to be performed during encryption communication processed by the server. If you set up an SSL certificate on the load balancer while setting up HTTPS/SSL, you do not need to set up SSL certificates on the individual servers that are connected.
- Ways to Distribute Server Load
- The server load distribution methods are Round Robin, Least Connection, and Source IP Hash.
· Round Robin: Delivers requests equally and sequentially to specified servers
· Least Connection: Assigns requests to a server with the fewest number of connections
· Source IP Hash: Carries out load balancing, with the result hashed on client’s source IP information
Provides Various Server Load Distribution Algorithms as Well as
Convenient Management Features for Stable Service
SSL Authentication and Encryption Settings
You can add an SSL certificate on the web-based console. You can select one version from SSL protocols, such as TLS v1, TLS v1.1, and TLS v1.2 and set the applied SSL ciphers. The load balancer allows the selected ciphers for connection during SSL connection.
Load Balancer Access Control Group (AGC) Settings
To establish communication between a load balancer and a server, the ACG rule that allows communication with the load balancer must be set. If the ACG rule is not set, successful communication is not possible even if load balancer Setup has been completed.
Load Balancer Port Settings
You can set several load balancer rules at a time. When setting a load balancer rule, you must set the load balancer port to be different from load balancer ports with other load balancer rules. The server port can be identical to the server port of other load balancer rules.
Load Balancer Monitoring
Basic monitoring information is provided for the load balancer. Like server monitoring, the monitoring information collection interval is 1min, 5mins, 2hrs, or 1 day. Load balancer monitoring provides three types of information: Concurrent Connections, Connections Per Second, and Traffic.
Load Balancer Management
After creating a load balancer, you can change the settings of Connection Idle Timeout or Keep-Alive. Connection Idle Timeout indicates the period to maintain the connection with the load balancer. Generally, the connection is forcibly disconnected after the period expires. If you need an application that supports long transactions, adjust the Connection Idle Timeout options to set the connection period. Additionally, when requesting a connection again while maintaining a connection for a certain period, you can reuse the existing connection with the HTTP Keep-Alive option.
Ways to Distribute Server Load
The supported server load distribution methods are: Round Robin, Least Connection, and Source IP Hash.
|Round Robin||Delivers requests fairly and sequentially to servers specified for load balancing. |
Regardless of the number of connections to the server or the response time from the server, processing is done for all servers included in the server, providing the fastest request processing speed when compared to a general configuration.
|Least Connection||Assigns the client's request to a server with the fewest number of connections.|
Allows the most efficient traffic distribution when there are multiple servers and the performance of all servers are similar to each other.
|Source IP Hash||Load balancing is performed using the results of hashing based on the client's source IP information. |
The use of the source IP hash algorithm is recommended when the SSL protocol is used.
The Load Balancer fee includes a base rate for each load balancer and a rate based on the amount of network traffic required to process data.
A basic fee is charged per load balancer.
|Load Balancer (per unit)||26 KRW|
If one load balancer is used for one month (30 days), the basic fee is 18,720 won for the month.
Load balancer network fee
Traffic handled by the load balancer is added to the network traffic which occurred in the other services (Server, File Storage, etc.) and charged together monthly.
The network fee is charged only for outbound traffic.
|Classification||Networks||Unit||Usage Level||Meter Rate (monthly)|
|Inbound Traffic||All||GB||Same for all sections||Free||Free|
|Outbound Traffic||Traffic through the Internet|
(including traffic toward another region via public IP)
|GB||20GB or Less||Free||500 KRW|
|20GB–5TB||100 KRW||500 KRW|
|5TB–10TB||90 KRW||450 KRW|
|10TB–30TB||80 KRW||400 KRW|
|Over 30TB||70 KRW||350 KRW|
|Traffic within the same zone via a public IP||GB||Same for all sections||10 KRW||10 KRW|
|Traffic between different zones via a private IP||GB||Same for all sections||10 KRW||10 KRW|
|Traffic within the same zone via private IP||GB||Same for all sections||Free||Free|
If the usage hours for the month are 240hrs and the traffic sent (outbound) via the domestic Internet is 10TB, the monthly fee is
(240hrs x 26 KRW) + (5,100GB x 100 KRW) + (5,120GB x 90 KRW) = 6,240 KRW + 970,800 KRW = 977,040 KRW.