Load balancing

A load balancing solution is required to enable redundancy and for spreading the load across multiple Liquit Workspace servers.
We have tested the following load balancing solutions and they are supported by Liquit Systems:

• Kemp Load Balancer
• F5 BIG-IP
• Citrix ADC (NetScaler)
• Azure Load Balancer
• Azure Application Gateway (If WAF is used, then there is a file upload limit that can cause issues. For more information, see Microsoft documentation.)

The following solutions are not supported in production Liquit Systems because of known issues or limitations of the load balancing:

• Microsoft Network Load Balancing (NLB)
• Round Robin DNS

Configuration recommendations

• Enable session affinity (sticky session), to ensure user sessions are always handled by the same server. We recommend using the cookie-based session affinity. If not supported, a fallback could be Source IP. This ensures the proper use of caching within Liquit Workspace for optimal results.

• Configure health monitoring for each server on the following URL with a GET request: http://[Server IP]/api/server/status. This health check is designed to verify the web server, storage and database connectivity. When everything is verified, the API will respond with plain text containing "OK" as value. This configuration is mandatory for the server Maintenance mode feature.

• We strongly advise you to configure the internal and external DNS connectivity to use the same Virtual Host of a zone.