About Load Balancing
- 29 Jul 2022
- 1 Minute to read
- Print
- DarkLight
This documentation version is deprecated, please click here for the latest version.
About Load Balancing
- Updated on 29 Jul 2022
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Overview
When multiple application servers are being used with Decisions they are most commonly used with a load balancer. The load balancer acts as a primary point of contact so that all of the application servers look the same to any end-user. The load balancer internally routes data to each of the servers in the cluster based on criteria configured at the load balancer.
IMPORTANT!
When using a load balancer with Decisions, it is required that STICKY SESSIONS are included in the configuration. Cookie Based Session Persistence is recommended if available, this feature uses a cookie to uniquely identify a session and later references that cookie to push the connection to the appropriate server. Sticky Session makes sure that a particular user’s session interacts with the same server within the cluster for the duration of the session.
For more information about Clustering, please visit our About Clustering article.
SSL Passthrough
The use of SSL Passthrough at the Load Balancer is recommended over SSL Termination, as SSL Termination does not allow for the improvements and benefits of HTTP/2 to be utilized. For more information on the differences between HTTP/1.1 and HTTP/2, please visit this comparative article.
Azure Application Gateway/Cookie-Based Session
The following are the requirements for Backend pool of VMs with IIS/Decisions application:
- Configured as Decisions cluster
- No SSL termination on the IIS side (termination is completed on the AAG)
- SSL Offloading
- Increased performance from backend pool to AAG
The following are the requirements for Azure Application Gateway:
- SSL Termination
- Health check configuration
- HTTP/S redirect / rules configuration
- Requires separate Virtual Networks within the same address space of the backend pool.
- Cookie Session Affinity configuration
The following are the requirement for Decisions Configuration supporting AAG:
- Requires configuration for Cookie Affinity
Was this article helpful?
