It’s Saturday night. You realize you don’t have your cell phone and won’t be able to check on your fulfillment system. Chuckling, you remember without nostalgia the electric panic that used to set in over such a conundrum. Now you don’t give it a moment’s thought. After the weekend you arrive to work and try to avoid that blinking little red light, always in the periphery, nagging from the telephone set. Twenty-three more irate complaints demanding tedious, manual data forensics? Hardly, just a happy customer congratulating you on the vast improvement in your support center.
A dream? No, Mule 3.2 is here! The Mulesoft team is overjoyed to announce Mule 3.2, chock full of goodies for the enterprise and the Mule community.
High Availability Clustering
Ensuring zero message loss is a primary concern when you’re building mission-critical applications. Mule 3.2 provides key capabilities to support these applications. These capabilities include:
- High availability clustering to ensure system-level availability
- Reliability patterns for non-transactional connectors
Mule ensures system availability by clustering together Mule ESB servers into one virtual server composed of multiple nodes. The cluster acts as a unit, communicating and sharing information through a distributed shared memory data grid. If a node becomes unavailable due to failure or planned downtime, another node in the cluster can assume the workload and continue to process existing events and messages. Because all nodes in a cluster process messages simultaneously, clusters can also improve performance and scalability. Compared to a single node instance, clusters can support more users or improve application performance by sharing the workload across multiple nodes or by adding nodes to the cluster.
A zero-message loss application not only requires the underlying ESB to be reliable, but that reliability needs to extend to individual connections. New reliability patterns introduced in Mule 3.2 give you the tools to build fully reliable applications in your clusters. The Mule 3.2 documentation provides code examples that show how you can implement a reliable message pattern for a number of different non-transactional transports, including HTTP, FTP, File, and IMAP. (Mule’s built-in support for transactional transports such as JMS enables reliable messaging for applications that use these types of transports.)
Business Event Analyzer
Many businesses require accurate analysis of business events. Some use case examples include:
- Root cause analysis
- Regulatory compliance
- Business activity monitoring
- Business intelligence
Mule gives you in-depth visibility into business transactions and events on your Mule servers. This visibility is available out of the box in the Business Events tab in the management console. However, it can also be integrated with other applications through storage in a persistent database. You can track events for the flows and message processors handling your business transactions and drill down into event-related data to do things like analyze the root cause of failures, isolate performance bottlenecks, and test for compliance to company procedures.
With the availability, reliability, manageability, and visibility provided by Mule 3.2 you can achieve peace-of-mind that only comes from a truly world-class enterprise system.
But There’s Even More!
- Store and Forward with the new until-successful message processor. You can use the until-successful to retry an operation until it succeeds. For example, you can configured it to send a message to an outbound endpoint until the send succeeds.
- Mule’s support for the async request-reply messaging style has been extended to flows where previously it was available only to services
- Mule is now much smarter about how it handles concurrency. Mule 3.2 Processing Strategies give you more flexibility in the way flows are processed
- Achieve better flow performance by storing events in SEDA queues where previously SEDA queues were available only to services
- Use configurable object stores to control how SEDA events are persisted
- Manage Mule servers and clusters with a full complement of REST management API’s
- Use Drools for complex workflows and complex event processing (CEP)
- Use sophisticated class loading control and plugin packaging for even more robust application modularity
- Mule 3.2 is enabled for internationalization and localization across the entire product
Download Mule 3.2
Download Mule 3.2 at http://www.mulesoft.org/download. Be sure to check out what’s new in Mule 3.2 for detailed information on this release.