Definition – Load Balancer Persistence
Load balancers play a crucial role in distributing incoming network traffic across a pool of servers to ensure efficient resource use, optimize throughput, and reduce response time. To manage sessions effectively, especially when sessions need to maintain state, load balancers utilize various types of persistence mechanisms. These mechanisms ensure that requests from the same client are directed to the same server for the duration of a session. Let’s explore the different types of persistence techniques commonly used in load balancers
Different Types of Load Balancer Persistence
1. Cookie-Based Persistence
How it works:
- The load balancer injects a session cookie into the HTTP response from the server to the client. This cookie typically contains a unique session identifier or server identifier.
- The client’s browser stores this cookie and includes it in all subsequent requests.
- When the load balancer receives further requests with the cookie, it directs these requests to the server specified by the cookie.
Pros:
- Works with any client that accepts cookies.
- Easy to implement and transparent to users.
Cons:
- Not suitable for non-browser clients that may not handle cookies.
- Dependence on client behaviour (cookies must be enabled and preserved).
2. IP Hashing
How it works:
- The load balancer applies a hash function to the source IP address of incoming requests to determine which server will handle the request.
- The same IP address always results in the same hash output, directing the requests to the same server, provided the server pool remains unchanged.
Pros:
- Simple to implement and does not require tracking sessions.
- Works automatically with any client.
Cons:
- If a client’s IP address changes (e.g., mobile users), persistence is lost.
- Does not adapt well to changes in the number of servers (scaling operations can disrupt session persistence).
3. Source IP Affinity
How it works:
- Similar to IP hashing, but the load balancer may maintain a table mapping client IPs to specific servers.
- This mapping can be more dynamic, allowing for adjustments based on server load and availability.
Pros:
- More flexible than simple IP hashing.
- Maintains persistence even with dynamic changes in the server environment.
Cons:
- Requires more memory and processing power to maintain the mapping table.
- Still vulnerable to issues if client IP changes.
4. SSL/TLS Session ID
How it works:
- The load balancer uses the SSL/TLS session ID created during the SSL handshake between the client and the server.
- All requests with the same SSL/TLS session ID are directed to the same server that handled the original request.
Pros:
- Secure and effective for applications using SSL/TLS.
- Works without requiring cookies or IP-based methods.
Cons:
- Only applicable for SSL/TLS traffic.
- Requires access to the SSL/TLS session ID, which may not be possible with encrypted SSL traffic if the load balancer does not terminate the SSL connection.
5. Custom Headers
How it works:
- Applications or clients include a custom header in HTTP requests.
- The load balancer reads this header and uses its value to direct requests to a specific server.
Pros:
- Highly flexible and configurable.
- Useful for applications that can manage their header content effectively.
Cons:
- Requires modifications to client or application code.
- Depends on the integrity and consistency of header data.
6. Parameter-Based Persistence
How it works:
- The load balancer uses a specific parameter within the client request (like a URL parameter or a form field) to determine the server assignment.
- The parameter value is hashed or directly mapped to select a server.
Pros:
- Allows fine-grained control over load distribution.
- Useful for specific applications where session IDs or unique parameters are part of the request.
Cons:
- Requires that all requests include the necessary parameter.
- Potential for parameter manipulation by clients.
Conclusion – Load Balancer Persistence
Load Balancer Persistence – Choosing the right persistence method depends on the specific requirements and constraints of your application and network environment. Considerations include client behaviour, security requirements, scalability needs, and the acceptable complexity of implementation. Each method has its advantages and trade-offs, making it essential to align the choice with the operational goals and technical capabilities of your environment.
Useful Links – Load Balancer Persistence
https://sanchitgurukul.com/proxy
