Skip to main content

 –

Architecting a high availability system

Suggest edit Updated on August 25, 2021

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 high availability architecture

Architecting a high availability system involves setting up the components of the highly available system and then defining highly available integration services.

  1. Setting up the components of highly available environments

    Creating a highly available system typically requires coordination across multiple groups in an organization. Individuals or groups responsible for deploying highly available systems must collectively understand and agree on how to configure the Pega Platform for their organization.

  2. Defining highly available integration services

    Deployments of Pega Platform integration services that are part of highly available production environments require additional configuration that might not be necessary in development.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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