For an organization migrating its Mule applications and load balancer to CloudHub while preserving its public URL, the most straightforward and cost-effective approach involves leveraging CloudHub's shared load balancer (SLB). Here’s how to do it:

Deploying Mule Applications to CloudHub:

First, deploy your Mule applications to CloudHub. This involves packaging your Mule applications and using the Anypoint Platform to deploy them to CloudHub.

DNS Configuration:

Update your DNS settings to ensure the base URL (https://api.rutujar.com ) points to the CloudHub shared load balancer. Specifically, create or update a CNAME record for api.rutujar.com to point to the CloudHub SLB's A record.

Configuring Shared Load Balancer (SLB):

In CloudHub, configure the SLB to handle incoming traffic and route it to the appropriate Mule applications.

Apply mapping rules in the SLB to map the base URL and its paths to the corresponding Mule applications. This ensures that requests to https://api.rutujar.com are correctly routed to the specific Mule application endpoints.

Steps to Apply Mapping Rules:

In Anypoint Platform, navigate to the Runtime Manager and select the application deployed on CloudHub.

Configure the SLB settings by defining the domain and URL mappings. For instance, set rules that map requests from https://api.rutujar.com/app1 to the corresponding Mule application app1.

Benefits of Using SLB:

Cost-Effective: The shared load balancer is a more economical option compared to a dedicated load balancer (DLB).

Simplicity: Using SLB simplifies the deployment process, as it requires less configuration and management compared to setting up and maintaining a dedicated load balancer.

Consistency: Preserves the public-facing URL structure, ensuring a seamless transition for users and clients accessing the APIs.

References:

MuleSoft Documentation on CloudHub Deployment

MuleSoft Documentation on Shared Load Balancer

By following these steps, the organization can effectively migrate its applications to CloudHub, ensuring minimal disruption and preserving the existing public URL structure.