CloudHub Load Balancers
Shared Load Balancers
CloudHub provides a default shared load balancer that is available in all environments. The shared load balancer provides basic functionality, such as TCP load balancing. Shared load balancers don’t allow you to configure custom SSL certificates or proxy rules.
Additionally, shared load balancers have lower rate limits that help ensure platform stability. MuleSoft regularly monitors and scales these limits as necessary. Rate limits on shared load balancers are applied according to region. If you are deploying an application to workers in multiple regions, the rate limit for each region might be different.
If an application exceeds the rate limit for a shared load balancer, the load balancer returns a 429 Service Unavailable response.
To perform custom load balancer configuration or have higher rate limit thresholds, you must use a dedicated load balancer.
The shared load balancer supports TLS versions 1.1 and TLS 1.2.
Dedicated Load Balancers
Dedicated load balancers enable you to:
-
Handle load balancing among the different CloudHub workers that run your application.
-
Define SSL configurations to provide custom certificates and optionally enforce two-way SSL client authentication.
-
Configure proxy rules that map your applications to custom domains.
This enables you to host your applications under a single domain.
Dedicated load balancers are an optional component of Anypoint Platform.
For information about dedicated load balancers, see Dedicated Load Balancers.
Load balancers do not currently support HTTP streaming. When a call is made directly to the worker, HTTP streaming behavior occurs as expected (that is, an error response is received before the full attachment is uploaded). However, when you make a call to the load balancer, you don’t receive the response until the full upload completes, which can take several minutes. |