Enterprise Integration Patterns
This page describes the Enterprise Integration Patterns which form the foundation of Camel. If you are new to Camel you might want to try the Getting Started in the User Guide before attempting to implement these patterns.
Messaging Systems
|
How does one application communicate with another using messaging? |
|
|
How can two applications connected by a message channel exchange a piece of information? |
|
|
How can we perform complex processing on a message while maintaining independence and flexibility? |
|
|
How can you decouple individual processing steps so that messages can be passed to different filters depending on a set of conditions? |
|
|
How can systems using different data formats communicate with each other using messaging? |
|
|
How does an application connect to a messaging channel to send and receive messages? |
Messaging Channels
|
How can the caller be sure that exactly one receiver will receive the document or perform the call? |
|
|
How can the sender broadcast an event to all interested receivers? |
|
|
What will the messaging system do with a message it cannot deliver? |
|
|
How can the sender make sure that a message will be delivered, even if the messaging system fails? |
|
|
What is an architecture that enables separate applications to work together, but in a de-coupled fashion such that applications can be easily added or removed without affecting the others? |
Message Routing
|
How do we handle a situation where the implementation of a single logical function (e.g., inventory check) is spread across multiple physical systems? |
|
|
How can a component avoid receiving uninteresting messages? |
|
|
How do we route a message to a list of dynamically specified recipients? |
|
|
How can we process a message if it contains multiple elements, each of which may have to be processed in a different way? |
Message Transformation
|
How do we communicate with another system if the message originator does not have all the required data items available? |
|
|
How do you simplify dealing with a large message, when you are interested only in a few data items? |
|
|
How do you process messages that are semantically equivalent, but arrive in a different format? |
Messaging Endpoints
|
How do you move data between domain objects and the messaging infrastructure while keeping the two independent of each other? |
|
|
How can an application automatically consume messages as they become available? |
|
|
How can an application consume a message when the application is ready? |
|
|
How can a messaging client process multiple messages concurrently? |
|
|
How can multiple consumers on a single channel coordinate their message processing? |
|
|
How can a message consumer select which messages it wishes to receive? |
|
|
How can a subscriber avoid missing messages while it's not listening for them? |
|
|
How can a message receiver deal with duplicate messages? |
|
|
How can a client control its transactions with the messaging system? |
|
|
How do you encapsulate access to the messaging system from the rest of the application? |
|
|
How can an application design a service to be invoked both via various messaging technologies and via non-messaging techniques? |
System Management
|
How do you inspect messages that travel on a point-to-point channel? |