We all have been aware of patterns existing in all forms of solution. In this post, I would like to give you a overview of the patterns that are recommended to be followed in Enterprise Integration.
The usage of these patterns depends on the need of the solution. Lets get started!
Messaging
This is basic pattern for System Integration to exchange information. On a high level, this makes use of a message bus.
Message Channel
This describes how two systems should communicate. The Channel is used to write and read information between two systems.
Message
What information should be exchanged between Sender and Receiver. This also details how the information should be structured.
Pipes and Filters
This pattern details how and what processing steps should be in between sender sending the message and receiver reciving the same. There can be many operations – encryption, decryption etc.
Message Router
This routes the message from one sender to multiple receiver or select one of multiple receiver possible based on the message property or configuration.
Message Translator
This is majorly used as the two systems integrating in today’s world will anyway have different message format requirement. Hence Translator.
Message Endpoint
This is a technical aspect of the pattern which creates a client on each sender/receiver to communicate asynchronously.
The details of each pattern will follow in consecutive posts. Keep a track!
Below is a site map for the Enterprise Integration Patterns:
My first time visiting your blog, and here I found a lot of interesting content .. thanks for sharing .
Glad you like the content!