Do you have high availability requirements for your Mule application? Mule High Availability provides basic failover capability for Mule. When the primary Mule instance become unavailable (e.g., because of a fatal JVM or hardware failure or it’s taken offline for maintenance), a backup Mule instance immediately becomes the primary node and resumes processing where the failed instance left off. After a system administrator has recovered the failed Mule instance and brought it back online, it automatically becomes the backup node.
Seamless failover is made possible by a distributed memory store that shares all transient state information among clustered Mule instances, such as:
- SEDA service event queues
- In-memory message queues
Mule High Availability is currently available for the following transports:
- HTTP (including CXF Web Services)
- JMS
- WebSphere MQ
- JDBC
- File
- FTP
- Clustered (replaces the local VM transport)
To learn more about the high availability solution, check out the following resources:
- A podcast in which MuleSource Sr. Director of Engineering Ken Yagen joins me in a brief conversation introducing the high availability solution
- A solution overview that provides additional technical information and installation highlights
- The Mule High Availability documentation page on the MuleSource public wiki (login is required, but registration is free and only takes a moment)
Mule High Availability is available for Mule ESB Enterprise Platinum subscribers. To download a free evaluation copy on a trial basis, contact MuleSource.
