Receive a message that contains multiple logical items.
Message Routing
Composed Message Processor
Combine splitting, routing and aggregation into a coordinated flow that processes each element correctly and rebuilds a meaningful result.
How can you maintain the overall message flow when processing a message consisting of multiple elements, each of which may require different processing?Adapted from Enterprise Integration Patterns under CC BY 3.0. The visualization and explanatory content on this page are original GateSift material.
Original GateSift visualization
How Composed Message Processor works
One larger message is divided into smaller messages that can be processed independently.
Composite message
Composed Message Processor
Part A
Part B
Part C
Apply Composed Message Processor to identify and emit the individual parts.
Process each emitted message independently, often in parallel.
What this pattern helps you decide
Combine splitting, routing and aggregation into a coordinated flow that processes each element correctly and rebuilds a meaningful result.
What happens when processing fails or the same message is delivered twice?
Where does state, correlation or routing configuration live?
How will operators trace the message and understand the decision path?
Where you may see it
- Durable Functions fan-out/fan-in
- Logic Apps split-and-join workflow
- BizTalk orchestration with maps
How the analyzers can surface it
- Composite branch and join flows
- Splitter plus aggregator behavior
Pattern detection is contextual. GateSift should present these as architectural signals, not claim a pattern is implemented solely because one policy statement or adapter exists.
Source, licence and attribution
The pattern name and selected problem statement are adapted from Enterprise Integration Patterns by Gregor Hohpe and Bobby Woolf under CC BY 3.0. GateSift summaries, Azure mappings, analyzer guidance and diagrams are original. No endorsement by the original authors is implied.