Explanation for re-engineering of Process Integration application patterns
The patterns ordered by type of coordination in EAI process and type of request:
| Application Coordinated | Transactional Coordinated | Brokered Coordinated |
Process Managed
(BPM) Coordinated |
|
|---|---|---|---|---|
| Information Request (IR) | Direct Connection | N/A | Aggregator | N/A |
| Processing Request (PR) | Direct Connection | Transactional | Broker | Managed Process |
The old and new pattern names:
| Old Pattern Name | New Pattern Name |
|---|---|
| Application Coordinated | Direct Connection |
| Transactional Coordinated | Becomes QoS |
| Brokered Coordinated | Broker |
| Process Managed (BPM) Coordinated |
Split into:
|
The Process Integration patterns have been re-engineered because:
- The distinction between R/O Information Requests and R/W Processing Requests was not found to be significant
- The distinction between Aggregator and Broker was not found to be significant
- The type of coordination was not found to be the most important characteristic by which to distinguish the patterns
- Transactionality is now defined as a QoS which can apply to any pattern
- More modern middleware provided richer process management options
- The new patterns can be applied fractally to Process Integration problems
The retired Application Integration patterns can be found in a zip on the Resource page. Download (ZIP, 815KB)
Return to the Process Integration patterns.
