QuestionQ41

VerifiedDesigning for the runtime plane technology architecture

An organization has selected a cloud-migration strategy to minimize the organization’s own ГГ resources. At present, all of the organization’s Mule applications run on its own premises, and it uses an on-premises load balancer that exposes all APIs under the base URL https://api.acme.com.

As part of the migration strategy, the organization plans to move all of its Mule applications and the on-premises load balancer to CloudHub 1.0.

What is the simplest and most cost-effective approach to Mule application deployment and load balancing that retains the public URLs?

Explanation

A CloudHub 1.0 Dedicated Load Balancer supports custom domains and URL proxy/mapping rules, allowing a DNS CNAME for api.acme.com to direct traffic to the DLB and route each URL to its corresponding Mule application. CloudHub Shared Load Balancers provide only basic load balancing and do not support custom proxy rules or custom SSL certificates, so they cannot provide this routing arrangement. Deploying extra proxy applications adds unnecessary applications and operational cost.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!