The purpose of this example is to demonstrate how WSO2 ESB could be used to implement Message Sequence EIP pattern. When transmitting large data it is necessary to chunk the messages in order to maintain the performance of the system.
Compatibility of WSO2 ESB
When the request which is sent is large WSO2 ESB will by default chunk message into smaller sizes. In order to maintain the consistency of the message each chunk will be mapped with a sequence identity number.
...
| hidden | true |
|---|
...
This section explains how the Message Sequence EIP can be implemented using WSO2 ESB. The following topics are covered:
| Table of Contents |
|---|
Introduction to Message Sequence
When transmitting a large set of data, you might want to break it into smaller chunks in order to maintain system performance. The Message Sequence EIP facilitates this by sending data as a sequence of smaller messages and marking each message with sequence identification fields. For more information, refer to http://www.eaipatterns.com/MessageSequence.html.
How WSO2 ESB implements the EIP
When the sent request is large, WSO2 ESB by default breaks it into smaller chunks. In order to maintain consistency of the message, each chunk is then mapped with a sequence identity number so that its sequential order is not lost.