MuleSoft load balancer architecture

Views:
 
Category: Education
     
 

Presentation Description

It is a process of distributing network traffic across multiple servers. This ensures no single server bears heavy demand. Application responsiveness increases by spreading the work evenly in the load balancers. The load balancers also have additional capabilities including security and application. In this article, let us see about MuleSoft load balancer architecture.

Comments

Presentation Transcript

slide 1:

Overview of MuleSoft load balancer architecture. Load balancer: It is a process of distributing network traffic across multiple servers. This ensures no single server bears heavy demand. Application responsiveness increases by spreading the work evenly in the load balancers. The load balancers also have additional capabilities including security and application. In this article let us see about MuleSoft load balancer architecture. MuleSoft Cloudhub: CloudHub is a software integration platform as a service iPaaS. Through this you can deploy advanced cloud-based cross-cloud integration applications. You can also build new APIs in addition to existing data sources. Integrate on-site apps with cloud services and more. Mulesoft cloud hub comes with two types of load balancers. ● Shared load balancer ● Dedicated load balancer Shared Mulesoft Load balancer architecture: CloudHub offers a virtual MuleSoft load balancer architecture by design. It is usable in all environments. The MuleSoft load balancer architecture provides a basic feature including balancing TCP load. Cloud hub Shared load balancers do not require you to set up custom SSL certificates or rules for the proxy. Besides shared load balancers have lower speed limits which help to ensure the stability of the platform. MuleSoft tracks and scales those limits as appropriate regularly. The users should pay tariffs based on their area. If you distribute a job application to staff in several regions the rate cap may be different for each region. The Mulesoft load balancer architecture is mentioned in the figure below. For more info Mulesoft Online Training

slide 2:

Dedicated Mulesoft load balancer architecture: CloudHub dedicated load balancers DLBs is an optional Anypoint Platform feature that allows you to redirect external HTTP and HTTPS traffic to multiple Mule applications in a Virtual Private Cloud VPC for CloudHub employees. Dedicated load balancers allow you to: ● Manage load balancing among the various CloudHub employees running your application. ● Defines SSL configurations to include unique certificates and optionally enforces SSL client authentication in two directions. ● Set up proxy rules which map your applications to custom domains. That allows you to host your applications within a single domain. Info on Mule Training

slide 3:

Mulesoft Load balancer architecture DLB: Shared load balancer v/s dedicated load balancer: ● The External IP sits directly on the Load Balancer with the Shared Load Balancers.The VIP is an internal Pc with a Dedicated Load Balancer. To have external entry the firewall must be fitted with a MIP / NAT. This will connect to the internal VIP. ● A customer wants to use a Load Balancer to access an internal VIP to the VPN platform via their domain a dedicated Load Balancer is required. Connection to an internal VIP on the Shared Load Balancer over a network to a VPN domain is not feasible. ● Shared Load Balancers are in a pair of High Accessibility. When any node goes down then no downtime will occur. Dedicated load balancers can be mounted on request into an HA pair. ● Dedicated Load Balancer service is limited in that Customer Care engineers must confirm the state of infrastructure and virtual machine status. Then the customers are responsible for both Day 1 2 and N operational services. Learn from Mule 4 Training When should you use a dedicated Load balancer In the previous paragraph you may have come to an idea of shared and dedicated load balancers. In a shared load balancer you deploy the application under the hood in CloudHub. Then a new runtime worker from Mule is developed. At the same time a default Mulesoft load

slide 4:

balancer architecture will generate a route to the requests for the API to the workers of Mule. For example the public URL would be https:/space-station.cloudhub.io. It is the name for the deployment i.e. space station. The API will be open to the public and will be load balancing when assigned to several employees. Make sure you connect the URL to A Cloud hub. A shared load balancer API will be open to the public.If I want to use the domain for my employees and organization then I should go for a dedicated load balancer. This helps in controlling and managing your API as per the organizations policies. Configuring dedicated Mulesoft load balancer architecture: ● Open Anypoint platform click runtime manager. ● You should click on the load balancer. Then click on create a load balancer. ● Then give a name to your load balancer. ● Then you should select the target AnyPoint VPC from the drop-down list. ● In the Timeouts in the second’s field specify the amount of time DLB waits for a response. ● Give the domain routing as per requirements. ● Perform Inbound http selection of a load balancer ● Add a certificate. ● Then click on create the load balancer. Conclusion: In this article I discussed the MuleSoftload balance architecture. You can use a load balancer to manage your data in the cloud. You can learn more about the MuleSoft load balancer architecture and work through Mulesoft Training

authorStream Live Help