Understanding Enterprise Integration Patterns Using Mule
The Enterprise Integration Patterns are accepted solutions to recurring problems within a given context and they provide a framework for designing, building messaging and integration systems as well as a common language for teams to use when architecting solutions.
Mule supports most of the Enterprise Integration Patterns from the book by Gregor Hohpe and Bobby Woolf.
The fact that Mule implements these patterns greatly reduces the effort required when building integrations. You can design your solution using these well-known patterns and then simply configure and use these same patterns in Mule.
Mapping Enterprise Integration Patterns into Mule Objects.
There is a list of patterns that can be mapped directly with Mule objects. Find the list of Enterprise Integration Patterns mapped to Mule objects below:
Integration Styles
| Pattern | Mapping to a Mule Object |
|---|---|
File Transfer |
|
Shared Database |
|
Messaging |
Mule is all about Messaging |
Messaging Systems
| Pattern | Mapping to a Mule Object |
|---|---|
Message Channel |
Mule provides a message channel that connects the message processors in a flow. |
Pipes and Filters |
A Flow implements a pipe and filter architecture |
Message Router |
|
Message Translator |
|
Message Endpoint |
Inbound & Outbound Endpoints |
Messaging Channels
| Pattern | Mapping to a Mule Object |
|---|---|
Point-to-Point Channel |
The default channel within a flow. |
Message Bus |
Mule is a message bus. |
Message Routing
| Pattern | Mapping to a Mule Object |
|---|---|
Content-Based Router |
|
Message Filter |
|
Recipient List |
|
Splitter |
Collection Splitter, Message Chunk Splitter & Plain Splitter |
Aggregator |
Collection Aggregator, Message Chunk Aggregator & Custom Aggregator |
Resequencer |
Messaging Endpoints
You can declare endpoints to be transactional as needed.
| Pattern | Mapping to a Mule Object |
|---|---|
Idempotent Receiver |
Idempotent Message Filter |