#173 Pattern description
This commit is contained in:
parent
767f41ad90
commit
0aa84e37f2
@ -11,10 +11,22 @@ tags:
|
||||
---
|
||||
|
||||
## Intent
|
||||
It is very common in integration systems that incoming messages consists of many items bundled together. For example
|
||||
an invoice document contains multiple invoice lines describing transaction (quantity, name of provided
|
||||
service/sold goods, price etc.). Such bundled messages may not be accepted by other systems. This is where splitter
|
||||
pattern comes in handy. It will take the whole document, split it based on given criteria and send individual
|
||||
items to the endpoint.
|
||||
|
||||

|
||||
|
||||
## Applicability
|
||||
Use the Splitter pattern when
|
||||
|
||||
* You need to split received data into smaller pieces to process them individually
|
||||
* You need to control the size of data batches you are able to process
|
||||
|
||||
## Credits
|
||||
|
||||
* [Gregor Hohpe, Bobby Woolf - Enterprise Integration Patterns](http://www.enterpriseintegrationpatterns.com/patterns/messaging/Sequencer.html)
|
||||
* [Apache Camel - Documentation](http://camel.apache.org/splitter.html)
|
||||
|
||||
|
BIN
eip-splitter/etc/sequencer.gif
Normal file
BIN
eip-splitter/etc/sequencer.gif
Normal file
Binary file not shown.
After Width: | Height: | Size: 2.2 KiB |
Loading…
x
Reference in New Issue
Block a user