Enable necessary modules such as mod_proxy, mod_proxy_http, mod_proxy_balancer; 2. Configure BalancerMember in VirtualHost to define the backend server and use ProxyPass to distribute traffic; 3. Optionally configure stickysession to achieve session retention; 4. Use ping parameters to perform basic health checks on the backend server; 5. Enable balancer-manager page to perform monitoring and management; Apache's proxy module can quickly build a lightweight load balancer, suitable for small and medium-sized applications. If you need higher performance, it is recommended to use HAProxy or Nginx.

Using Apache as a load balancer is a practical and cost-effective solution when you want to distribute incoming web traffic across multiple backend servers. Apache achieves this using the mod_proxy and mod_proxy_balancer modules, along with optional health checks and session persistence.

Here's how to set it up step by step:

? 1. Enable Required Apache Modules

First, make sure the necessary modules are enabled. These are usually included in standard Apache installations.

On Ubuntu/Debian :

 sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod proxy_balancer
sudo a2enmod lbmethod_byrequests # Optional: for request-based load balancing
sudo a2enmod slotmem_shm # Required for in-memory session storage

On CentOS/RHEL (in httpd.conf or via command):

 sudo yum install httpd
# Then ensure modules are loaded in config, or use:
sudo systemctl enable httpd

Modules needed:

• mod_proxy
• mod_proxy_http (for HTTP/HTTPS proxying)
• mod_proxy_balancer (core load balancer)
• mod_lbmethod_* (eg, byrequests , bytraffic , heartbeat )

Restart Apache after enabling:

 sudo systemctl restart apache2 # or httpd

? 2. Configure the Load Balancer in Apache

You can configure the load balancer inside a <VirtualHost> block or in your main site configuration.

Example: Balance traffic between three backend servers (eg, app servers running on port 8080):

 <VirtualHost *:80>
    ServerName myapp.example.com

    # Disable reverse proxy requests from being cached
    ProxyPreserveHost On

    # Define the load balancer group
    <Proxy "balancer://mycluster">
        BalancerMember http://192.168.1.10:8080
        BalancerMember http://192.168.1.11:8080
        BalancerMember http://192.168.1.12:8080
        ProxySet lbmethod=byrequests
    </Proxy>

    # Route all requests to the balancer
    ProxyPass "/" "balancer://mycluster/"
    ProxyPassReverse "/" "balancer://mycluster/"
</VirtualHost>

? Key Directives:

• BalancerMember : Adds a backend server.
• lbmethod=byrequests : Distributes requests evenly (round-robin). Other options:
  • bytraffic – by bytes sent
  • bybusyness – to least busy server
  • heartbeat – uses dynamic feedback (requires extra setup)
• ProxySet : Sets parameters for the entire balancer group.

? 3. Optional: Enable Session Persistence (Sticky Sessions)

If your app relies on sessions (eg, shopping carts), you may want users to stick to the same backend.

Use route parameters and configure your app to set a cookie like JSESSIONID .

Example:

 <Proxy "balancer://mycluster">
    BalancerMember http://192.168.1.10:8080 route=server1
    BalancerMember http://192.168.1.11:8080 route=server2
    ProxySet lbmethod=byrequests stickysession=JSESSIONID
</Proxy>

Your backend app must return a cookie like:

 Set-Cookie: JSESSIONID=abc123.server1

Apache will then route requests with JSESSIONID=*.server1 back to the first server.

? 4. Add Health Checks (Basic)

Apache doesn't have advanced health checks by default, but you can use ping parameter to probe backend liveness.

 BalancerMember http://192.168.1.10:8080 route=server1 ping=5

This sends a HEAD request every 5 seconds. If the backend doesn't respond with 2xx/3xx, it's marked as failed.

Note: For robust health checks, consider pairing with external monitoring or using a tool like mod_cluster .

? 5. Monitor the Load Balancer (Optional UI)

Enable the balancer manager interface to view and manage the cluster:

 <Location "/balancer-manager">
    SetHandler balancer-manager
    Require ip 192.168.1.0/24 # Restrict access
    # Require local # Or only allow localhost
</Location>

Then visit: http://myapp.example.com/balancer-manager to see status, enable/disable servers, etc.

? Summary of Key Points

• Apache acts as a reverse proxy load balancer using mod_proxy_balancer .
• Supports round-robin , traffic-based , and sticky sessions .
• Simple to set up and integrates well with existing Apache settings.
• Best for small to medium traffic; for high-scale or advanced needs, consider HAProxy , Nginx , or cloud solutions.

Basically, with just a few lines in your Apache config, you can distribute traffic and improve availability. It's not as fast or feature-rich as Nginx or HAProxy, but if you're already using Apache, it's a solid built-in option.

The above is the detailed content of How to use Apache as a load balancer?. For more information, please follow other related articles on the PHP Chinese website!