Misuse of orchestration – An orchestration engine provides automation and integration to manage complex cross-domain processes. It provides several facilities for versatility, resiliency, and auditing that would be excessive for simple operations that do not require this level of service. Do not use vCenter Orchestrator to replace single calls to the vCloud Director API.

Control of the workflows – The systems calling a vCenter Orchestrator should have a workflow throttling mechanism adjusted according to vCO-tested maximums to avoid resource starvation.

Load balancing – If maximums are exceeded, it may be necessary to design the system to load balance the workflows across different vCenter Orchestrator servers.

Orchestrated systems bottleneck – vCenter orchestrator workflows should have logic that prevents starting too many operations at once on the orchestrated systems. Design this logic to support the defined load. The parameters that have an influence on the started workload should be exposed as configuration elements to be adjusted by the Orchestration Administrator (a parameter that determines the number of vApp clones to be processed in parallel).