Introduction

Why a full chapter dedicated to multiple Orchestrators? Well... since Orchestrator became the central turning stone for vRealize automation, there are more and more customers that distribute and protect their Orchestrator infrastructure.

We differentiate between different goals and scenarios, such as high availability (HA), workload spreading, scaling out, and bandwidth optimization and localization. In the following sections I break this down into the three most common forms: cluster, distributed, and scale out designs.

Tip

Please note that the vRealize automation (vRA) internal Orchestrator should not be clustered as described here. If you scale out vRA, you should consider using an external Orchestrator cluster, not the built-in vRA Orchestrator. See Chapter 13, Working with vRealize Automation for more information.

Cluster design

As Orchestrator becomes more and more production-critical for companies, it is a solid idea to cluster Orchestrator to guarantee that it&apos...