mulemule-studiohigh-availabilitymule-componentmule-cluster

Things to be taken care while Moving from standalone to cluster Environment( High Availability)


Our application is currently running in standalone (on-premise), planning to move in to cluster(High Availability). Could be please let me know what all the possible Mule components and changes which i needs to be done in Developer point of view.

If you have already experience on migrating and any issues which should taken care. Your points really help me.Hope you understand the question. Please let me know if my questions needs further explanation. Thanks in advance.


Solution

  • In general, Mule automatically coordinates the resources and messages in a HA Cluster.

    For example:

    It's important to divide the flows in many steps and use VMs or JMS, so Mule can balance the messages across the nodes.

    Take a look to the documentation: https://docs.mulesoft.com/mule-user-guide/v/3.5/mule-high-availability-ha-clusters To see al considerations and recomendations.

    But in general you won't need to make major changes to your application, at most using VMs and JMS