Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Setting up load balancers

Suggest edit
Updated on April 5, 2022

User and service requests are passed through a load balancer to the Pega Platform servers. The Pega Platform server in turn makes requests to a database.

All load balancers for both on-premises and cloud Pega Platform installations use a single quiesce implementation. This allows for a quiesced node to have all users (both new and existing) be passivated immediately and for the node to be removed simultaneously.

In a highly available production system, the load balancer must have the following minimum requirements:

  • Session-based affinity support to ensure that requests from one user are directed to a specific application server that maintains the state for that user
  • Ability to disable a Pega Platform server or take the Pega Platform server out of the load balancer rotation to facilitate shutdown
  • Automatic active or passive Pega Platform server health monitoring for Pega Platform server failure detection
  • Scripting to manage cookies, invalidation, and optionally for allocation and deallocation of Pega Platform servers based on production load
Note: Highly available system architectures should support fail-over to a redundant load balancer.
  • Previous topic Setting up the components of highly available environments
  • Next topic Configuring session affinity for slow drain
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us