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.

Architecting a high availability system

Suggest edit
Updated on April 5, 2022

The Pega Platform supports production service level agreements and emphasizes redundancy as a best practice for physical and software-based highly available production architectures.

In the following diagram, redundancy is applied to the infrastructure across all tiers of the hardware and deployment architecture of Pega Platform servers, represented by the shadowed icons. For example, one implementation can have several load balancers, physical and virtual machines, shared storage repositories, and databases. These principles are general to three-tier architectures and are applicable to private hosting or cloud environments.

High availability architecture
Components of the high availability architecture

  • Previous topic Configuring nodes for high availability
  • Next topic Setting up the components of highly available environments
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