2aa9e78ddd
* Made minor changes in some patterns such as removed throws clause where not needed, changed incorrect order of arguments in assertEquals * Minor refactorings and code style changes. 1) Removed several use of raw types 2) Removed unnecessary throws clauses 3) Used lambda expressions wherever applicable 4) Used apt assertion methods for readability 5) Use of try with resources wherever applicable 6) Corrected incorrect order of assertXXX arguments * Removed unused import from Promise * Addressed review comments * Addressed checkstyle issue
layout, title, folder, permalink, categories, tags
| layout | title | folder | permalink | categories | tags | |||
|---|---|---|---|---|---|---|---|---|
| pattern | EIP Aggregator | eip-aggregator | /patterns/eip-aggregator/ | Integration |
|
Intent
Sometimes in enterprise systems there is a need to group incoming data in order to process it as a whole. For example you may need to gather offers and after defined number of offers has been received you would like to choose the one with the best parameters.
Aggregator allows you to merge messages based on defined criteria and parameters. It gathers original messages, applies aggregation strategy and upon fulfilling given criteria, releasing merged messages.
Applicability
Use the Aggregator pattern when
- You need to combine multiple incoming messages
- You want to process grouped data