Load Balancer overview
  • PDF

Load Balancer overview

  • PDF

Available in Classic and VPC

Load Balancer is a service distributing received traffic to multiple servers. It distributes received traffic to member servers registered to increase availability and adjust system utilization rate. This increases the workload's availability to support responding to unexpected server failures or scheduled change tasks without interruption.

Classic Load Balancer and Application Load Balancer/Network Load Balancer/Network Proxy Load Balancer are provided in Classic and VPC environments individually. So Load Balancer appropriate to the customer service can be selected.

A variety of features Load Balancer offers

Load Balancer supports VPC and Classic environments. 3 Load Balancer types are provided, depending on the environment in use.

Differed features are provided by environment and Load Balancer type. For features provided in the VPC environment, refer to VPC environment. For features provided in the Classic environment, refer to Classic environment.

VPC environment

Various features provided in the VPC environment by Load Balancer are as follows.

  • TCP high-performance load balancing (Network Load Balancer): Ensures performance from at least 100,000 to up to 400,000 connections per second, providing distributed processing performance optimized for the service size.
  • TCP session management (Network Proxy Load Balancer): Provides communications with proxy methods that can be used in TCP-based applications.
  • SSL authentication and encryption settings (Application Load Balancer, Network Proxy Load Balancer): Provides SSL protocols such as TLSv1/TLSv1.1/TLS1.2. Certificates can be managed by linking with the Certificate Manager service.
  • Various server load balancing methods (Application Load Balancer, Network Proxy Load Balancer: Provides 3 server load balancing methods.
    • Round robin
    • Least connection
    • Source IP hash
  • Provision of L7 (Application Layer) feature (Application Load Balancer): This is a rule supported by Load Balancer. Client's requests can be segmented to be delivered to servers.
  • Load Balancer monitoring: Provides monitoring information collected by a specific cycle.
  • Load Balancer port settings: Multiple Load Balancer rules can be applied simultaneously.

Classic environment

The various features provided in the Classic environment by Load Balancer are as follows.

  • SSL authentication and encryption settings: Certifications can be applied to Load Balancer and managed by linking with the Certificate Manager service.
  • Load Balancer port settings: Multiple Load Balancer rules can be applied simultaneously.
  • Load Balancer monitoring: Provides monitoring information collected by a specific cycle.
  • Manage Load Balancer: Connection idle time (time of maintaining connection to Load Balancer) and keep-alive (reusing the existing connection) settings can be changed after creating a Load Balancer.
  • Various server load balancing methods: Provides 3 server load balancing methods.
    • Round robin
    • Least connection
    • Source IP hash

About Load Balancer guide

Load Balancer provides services in Korea, Singapore, U.S. West, Hong Kong, Japan, and Germany regions. Since services provided vary in each region, different table of contents for the guides are provided as follows.

Korea and Singapore regions

Check the following table of contents and their details for smooth use of Load Balancer in the Korea and Singapore regions.

U.S. West, Hong Kong, Japan, and Germany regions

Check the following table of contents and their details for smooth use of Load Balancer in the U.S. West, Hong Kong, Japan, and Germany regions.

NAVER Cloud Platform provides a variety of related resources as well as the guide to help customers better understand Load Balancer. If you are a developer or marketer in need of detailed information while you are considering adopting Load Balancer or establishing data related policies, then make good use of the resources below.

Check FAQs First.

Q. What are the differences between public Load Balancer and private Load Balancer?

  • The differences between public Load Balancer and private Load Balancer are as follows.

    Type Public Load Balancer Private Load Balancer
    Method of use Use Load Balancer as DNS (domain name) Use Load Balancer with Virtual IP method
    Multizone support Load Balancer process can be created in either KR-1 or KR-2, or in both zones Load Balancer process is created in either KR-1 or KR-2
    Binding target server All owned servers are bound regardless of Load Balancer and server locations

Q. How many Load Balancers can I create?

  • The number of Load Balancers that you can create isn't limited.

Q. How many servers can be bound to a single Load Balancer?

  • One Load Balancer can bind up to 50 servers.

Q. Can multiple servers be applied to a single Load Balancer?

  • All servers in multiple zones can be applied to a single Load Balancer. Servers applied to other Load Balancers can also be applied.

Q. Which algorithms are supported by Load Balancer?

  • The algorithms supported by Load Balancer are as follows.

    Round Robin
    • How to deliver client requests fairly and sequentially for servers specified through load balancing
    • It is faster than other algorithms in a typical configuration since it equally handles all servers within a group, regardless of the number of server connections or response time.
    Least Connection
    • How to deliver client's requests to servers with the fewest client connections
    • Traffic distribution is most effective when servers' performance is configured similarly.
    Multizone support
    • Based on the results of the hash according to the client's Source IP address information, this is the method of delivering the client's requests to the server mapped to the client IP.
      • Source IP hash algorithm is recommended if SSL protocol is used.

    Q. What should I do to set the Load Balancer domain name to the domain for service?

    • Follow the procedures below to set the domain name.
      1. Click the Load Balancer to set the domain to check the connection information.
      2. Click the Services > Networking > Global DNS > Record menus, in that order.
      3. Click the [Add domain] button to add the domain.
      4. Click the [Add record] button.
      5. Enter the record name and enter the record value according to the following cases.
        • If it is added as A record, then enter the Load Balancer IP provided as A record for the domain name of the service you own.
        • If it is added as CNAME record, then enter the Load Balancer domain provided as CNAME record for the domain name of the service you own.
          • If the customer owns example.com domain
            networking-loadbalancer-loadbalanceroverview_cname
          • CNAME for zone apex (-root domain) can't be registered (RFC1033).
            networking-loadbalancer-loadbalanceroverview_cname2
      6. Click the [Add] button.
        • IPs viewed from the Load Balancer DNS name aren't fixed IPs, and they can be changed later. Make sure that you must not use the viewed public IPs instead of the provided DNS name by registering them directly to the service.
        • DNS names provided through Load Balancer aren't changed, so there is no impact if you registered with DNS names.

    Q. How do I create a Load Balancer?

    Q. Is it necessary to understand how the actions are linked to each other to define permissions by actions using the User Created policy?

    • When a specific action is selected to be granted to a sub account, the system automatically selects all actions that are linked to the chosen action.

    Was this article helpful?