If you want high availability with strong performance, which approach is preferred in a customer-hosted runtime plane?

If you want high availability with strong performance, which approach is preferred in a customer-hosted runtime plane?

• A. Clustering
• B. Load Balancing
• C. Neither
• D. OSv2

Answer: (B)

The main idea is to enable scale-out and resilience by distributing traffic across multiple runtime instances. In a customer-hosted runtime plane, you typically run several Mule runtimes and place a load balancer in front of them. The load balancer continually health-checks each node and routes incoming requests to the healthy instances. If one runtime goes down, the balancer automatically redirects traffic to the others, preserving uptime, while the added instances handle more requests in parallel to boost performance. Clustering can provide high availability by coordinating state across nodes, but it introduces complexity and synchronization overhead, which isn’t always necessary or desirable for many integrations—especially when apps are stateless or rely on external stores. OSv2 isn’t a deployment approach for HA or performance. So the practical, scalable choice for a customer-hosted setup is to use load balancing across multiple runtime nodes.

The main idea is to enable scale-out and resilience by distributing traffic across multiple runtime instances. In a customer-hosted runtime plane, you typically run several Mule runtimes and place a load balancer in front of them. The load balancer continually health-checks each node and routes incoming requests to the healthy instances. If one runtime goes down, the balancer automatically redirects traffic to the others, preserving uptime, while the added instances handle more requests in parallel to boost performance.

Clustering can provide high availability by coordinating state across nodes, but it introduces complexity and synchronization overhead, which isn’t always necessary or desirable for many integrations—especially when apps are stateless or rely on external stores. OSv2 isn’t a deployment approach for HA or performance. So the practical, scalable choice for a customer-hosted setup is to use load balancing across multiple runtime nodes.