It has now been nearly a month since Mule 3.4 was released and coming back from the 8 city tour Spring 2013 Mule summit, I can truly say there is tremendous excitement within the Mule community around the great features that this release offers.
In the coming weeks, key members of the MuleSoft team who were behind this release will be blogging about its various features and capabilities. Here is what this blog post line-up looks like:
Scalability, Reliability, High Performance: Your business demands it, Mule’s High Availability solution delivers. See why five of the world’s top 10 banks trust Mule to run their business. Join Muley’s Pablo La Greca and Ramiro Rinaudo for a live demonstration of the core components in MuleSoft’s robust High Availability solution.
- Setting up a cluster using the Mule Management Console
- Deploying an application to the cluster
- Demonstration of node failure when processing requests
- Demonstration of cluster recovery with zero message loss
- Discussion of the benefits of Mule’s Data Grid
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,