LoadBalancer Requirements - v2025.05
Product : Monosign
Version : v2025.05
Load Balancer Requirements
To ensure the application operates correctly behind a Load Balancer, the following configurations are recommended.
Load Balancing Policy
The Least Connection algorithm is recommended.
With this policy, incoming requests are directed to the server with the fewest active connections at any given time, ensuring balanced distribution of load across all backend nodes.
Protocol & Port
Setting | Value |
|---|---|
Protocol | HTTPS / TCP |
Port | 443 |
Since the application includes WebSocket connections, WebSocket support must be enabled on the Load Balancer.
SSL Offload
Setting | Value |
|---|---|
SSL Offload | Enabled |
A valid SSL certificate must be provided and configured on the Load Balancer.
Sticky Session (Session Persistence)
Sticky Sessions are not required by the application architecture.
Requests can be freely distributed across backend servers without session affinity.
Persistence Profile
Since Sticky Sessions are not used, no additional persistence profile definition is needed.
URL Redirection
No URL redirection rules are required for this application.
HTTP Header Rules
It is recommended to configure the Load Balancer to append the X-Forwarded-For header to all forwarded requests.
This allows the application to capture the real client IP address in its logs — particularly useful for auditing admin user access.
Access & Limit Policy
The application will not be publicly accessible. Access is restricted to the internal network only.
Therefore, rate limiting or similar traffic restriction policies are not required at this stage.
Backend Servers (Pool Members)
The Load Balancer must be authorized to reach the application servers on port 443.
No additional firewall rules or backend configuration is required beyond this port access.