The Apache Camel’s Enterprise Integration Patterns are inspired by a book of the same name written by Gregor Hohpe and Bobby Woolf. The patterns described by them provide an excellent toolbox for developing enterprise integration projects. In addition to providing a common language for discussing integration architectures, many of these patterns can be implemented directly via Apache Camel’s programming interfaces and XML configuration.
Name | Use Case | |||
|---|---|---|---|---|
Message Pattern | How can two applications connected by a message channel exchange a piece of information?Messaging System Patterns | When two independent applications need to exchange information, they can do so by transmitting data through a channel that connects the two. | ||
Message Channel PatternHow does one application communicate with another application using messaging?s | When two different applications or systems wish to exchange data, they can accomplish this by transmitting the data through a common channel that connects the two. | |||
Message Endpoint Pattern | How does an application connect to a messaging channel to send and receive messages? | |||
Pipes and Filters Pattern | How can we perform complex processing on a message while still maintaining independence and flexibility? | |||
Message Router Pattern | How can you decouple individual processing steps so that messages can be passed to different filters depending on a set of defined conditions? | Message Transformation Pattern | How do systems using different data formats communicate with each other using messaging?Routing Pattern | Describe various ways of linking message channels together, including various algorithms that can be applied to the message stream (without modifying the body of the message). |
The message transformation patterns describe how to modify the contents of messages for various purposes. |