Asynchronous Messaging Patterns

Asynchronous messaging enables applications to decouple from one another to improve performance, scalability, and reliability. This post will review the most common messaging patterns, along with why and when to use them. 

Nexmo brings real-time communication to MuleSoft apps

Nexmo MuleSoft API Connector

With the newly integrated Nexmo SMS API Connector now available on MuleSoft’s Anypoint Platform, mutual customers can easily integrate real-time messaging with their enterprise apps and data, and even create entirely new communication workflows to engage users and customers on a global basis.

Part 1: Changes to the Mule Message in Mule 4 Beta

September 7 2017

3 comments
mule 4 beta

The Mule 4 Beta release has a lot of new and improved functionality such as DataWeave and a refreshed Anypoint Studio experience, but we’ve also been busy under the hood making internal improvements to Mule runtime. In this series of posts, we’ll give a behind the scenes insight into what we have changed under the hood and why, along with the lowdown on what users need to know about the changes from an application design perspective.

Setting up queues and exchanges with Anypoint MQ

Messaging is used to help organizations provide reliable, zero message loss environments, to decouple applications, enable scale, and to unlock data for broader distribution.  It’s a critical pattern for most enterprise architectures.  In healthcare, for example, a messaging pattern might be used to create a buffer between the electronic medical records system and any number of consuming applications who need to know when a patient record has been updated.  Or in retail,

Messaging aka the Not So Enteprisey Integration Patterns

Picture cool kids in startups, cranking code as if their lives depend on it, focusing on the proverbial MVP above all else. At this stage, who cares if technical debt accumulates as fast as code gets written? It would be a waste of time and focus to try to keep the field as green as it was initially. Then the worst happens: the cool kids have it right, people love their new app and traffic starts to surge.

Synchronous and Asynchronous Throttling

motif

One of the most common use cases while building flows/applications in mule is to be able to communicate to external systems. The performance of that external system is often beyond the user’s control. It could be possible where the rate at which mule flow sends the messages outbound is faster than the rate at which that external system could process the message. In such scenarios, there is a need to be able to perform some kind of throttling so that we don’t burden/break the external system.

Integration Patterns: Message Filter

motif

In previous posts explaining the enterprise integration patterns with example Mule configuration I have covered Content-Enricher and Content-based Routing patterns, today I’ll talking about the “Message Filter” pattern.

Message Filter

How can a component avoid receiving uninteresting messages?

Use a special kind of Message Router, a Message Filter, to eliminate undesired messages from a channel based on a set of criteria.

Integration Patterns: Content-based Routing

motif

The implementation of the Enterprise Integration Patterns, first documented by Gregor Hohpe, is an important aspect of Mule.

These patterns are accepted solutions to recurring problems within a given context and as such provide both a framework for both designing and building messaging and integration systems as well as a common language for teams to use when architecting solutions.

The fact that Mule implements these patterns greatly reduces the effort required when building integrations,

Mule 3 Architecture, Part 1: Back to Basics

September 24 2010

1 comment.
motif

As you may have heard, Mule 3 has undergone a streamlining of its internal architecture. It’s now my job to explain what’s changed, why and what this means to you. I can’t promise it will be as exciting as a children’s movie but I will attempt to explain things as clearly as possible so that everyone can understand the concepts which in turn will help you use Mule 3 to its fullest.

Mule And ActiveMQ – A Perfect Match

September 17 2010

0 comments
motif

ActiveMQ in Action, an upcoming book from Manning Publications, may well end up being the perfect companion book for Mule In Action.

Happily Ever After…

Thanks to Mule ESB’s native support for Apache ActiveMQ and the capacity to transparently use Spring for advanced configuration needs, Mule has long been the ESB of choice to tap into ActiveMQ’s JMS goodness.