Enterprise Integration Patterns
This page describes the Enterprise Integration Patterns which form the foundation of Camel.
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 you decouple individual processing steps so that messages can be passed to different filters depending on a set of conditions? |
|
|
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? |
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? |
|
|
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 decoupled fashion such that applications can be easily added or removed without affecting the others? |
Messaging Endpoints
|
How can an application automatically consume messages as they become available? |
|
|
How can a message consumer select which messages it wishes to receive? |
|
|
How can a message receiver deal with duplicate messages? |
System Management
|
How do you inspect messages that travel on a point-to-point channel? |