Create a Linode account to try this guide with a $ credit.
This credit will be applied to any valid services used during your first  days.

Nearly every production application can benefit from a load balancing solution like Linode’s NodeBalancers. This guide covers how to get started with NodeBalancers, including how to architect your application, configure the NodeBalancer, and update the DNS.

Prepare the Application

To start using a NodeBalancer and benefiting from load balancing, your application should be stored on at least two Compute Instances. Each instance of your application should be able to fully serve the needs of your users, including being able to respond to web requests, access all necessary files, and query any databases. When determine your application’s infrastructure, consider the following components:

  • Application deployment: How will you deploy your application’s code and software infrastructure to each Compute Instance? Consider using automated git deployments or more advanced CI/CD tooling.

  • File storage and synchronization: Should the application’s files be stored alongside the application’s code or should you consider implementing a distributed storage solution on separate instances? For simple applications, consider file synchronization/backup tools like rsync or csync2. For a more robust solution, consider a distributed file system like GlusterFS.

  • Database replication: How will you maintain consistency between multiple databases? Consider the suggested architecture and available tooling for the database software you intend to use. Linode Managed Databases, when deployed with high availability enabled, are a great fully-managed solution. Alternatively, Galera is a self-hosted option that can be used with MySQL.

In some simple applications, the servers that store your application’s code can also store its files and databases. For more complex applications, you may want to consider designating separate application servers, file servers, and database servers. The application servers (where the web server software and application code resides) operate as the backends to the NodeBalancer. The file servers and database servers can be built on cloud-based solutions (like Managed Databases) or self-hosted software on Compute Instances.

For advice on load balancing and high availability, review the following resources:

Create the NodeBalancer

Once your application has been deployed on multiple Compute Instances, you are ready to create the NodeBalancer. Simple instructions have been provided below. For complete instructions, see the Create a NodeBalancer guide.

  1. Log in to the Cloud Manager, select NodeBalancers from the left menu, and click the Create Nodebalancer button. This displays the NodeBalancer Create form.

  2. Enter a Label for the NodeBalancer, as well as any Tags that may help you organize this new NodeBalancer with other services on your account.

  3. Select a Region for this NodeBalancer. The NodeBalancer needs to be located in the same data center as your application’s Compute Instances.

  4. Within the NodeBalancer Settings area, there is a single configuration block with sections for configuring the port, defining health checks, and attaching backend nodes. Additional ports can be added using the Add another Configuration button.

    The following recommended parameters can be used for deploying a website. For other applications or to learn more about these settings, see the Configuration Options guide.
    • Port: For load balancing a website, configure two ports: port 80 and port 443. Each of these ports can be configured separately. See Configuration Options > Port.

    • Protocol: Most applications can benefit from using the TCP protocol. This option is more flexible, supports HTTP/2, and maintains encrypted connections to the backend Compute Instances. If you intend to manage and terminate the TLS certificate on the NodeBalancer, use HTTP for port 80 and HTTPS for port 443. See Configuration Options > Protocol.

    • Algorithm: This controls how new connections are allocated across backend nodes. Selecting Round Robin can be helpful when testing (in conjunction with no session stickiness). Otherwise, Least Connections can help evenly distribute the load for production applications. See Configuration Options > Algorithm.

    • Session Stickiness: This controls how subsequent requests from the same client are routed when selecting a backend node. For testing, consider selecting None. Otherwise, Table can be used for any protocol and HTTP Cookie can be used for HTTP and HTTPS. See Configuration Options > Session Stickiness.

    • Health Checks: NodeBalancers have both active and passive health checks available. These health checks help take unresponsive or problematic backend Compute Instances out of the rotation so that no connections are routed to them. These settings can be left at the default for most applications. Review Configuration Options > Health Checks for additional information.

    • Backend Nodes: Each Compute Instance for your application should be added as a backend node to the NodeBalancer. These Compute Instances need to be located in the same data center as your NodeBalancer and have private IP addresses assigned to them. Set a Label for each instance, select the corresponding IP address from the dropdown menu, and enter the Port that the application is using on that instance. See Backend Nodes (Compute Instances).

      For most web applications that have the inbound ports 80 and 443 configured using the TCP protocol, you can set the backend nodes to use the same ports. If you are using the HTTPS protocol, TLS termination happens on the NodeBalancer and your Compute Instances should only need to listen on port 80 (unencrypted). If that’s the case, backend nodes for both inbound ports can be configured to use port 80.

  5. Review the summary and click the Create NodeBalancer button to provision your new NodeBalancer.

Update the DNS

After deploying your NodeBalancer and putting your application behind the NodeBalancer, the application can now be accessed using the NodeBalancer’s public IPv4 and IPv6 addresses. Since most public-facing applications utilize domain names, you need to update any associated DNS records. The A record should use the NodeBalancer’s IPv4 address and the AAAA record (if you’re using one) should use the NodeBalancer’s IPv6 address. See Manage NodeBalancers to view your NodeBalancer’s IP addresses. For help changing the DNS records, consult your DNS provider’s documentation. If you are using Linode’s DNS Manager, see Edit DNS Records. Keep in mind that DNS changes can take up to 24 hours to fully propagate, though that typically happens much faster.

This page was originally published on

Your Feedback Is Important

Let us know if this guide was helpful to you.