Updated May 5, 2026
Splitter (debatch)
One arrival, many messages. A batch file or multi-record envelope comes in; a splitter turns each item into its own canonical message on the bus.
Debatching happens in the receive pipeline. A disassembler pipeline component reads the envelope, an EDI interchange with many transactions, a CSV with many rows, a JSON array, and publishes one message per item, each classified separately. From that point the bus sees N independent messages, not one container.
The payoff is isolation: if item 2 is malformed, only item 2 is dead-lettered, items 1 and 3 sail through. Splitting is the inverse of the aggregator, and the two are often used as a pair to debatch, process per-item, then re-batch for a destination that wants one file.
Carry a batch key. Have the splitter component write the source interchange or file id into each item’s body, and promote it on the item’s message type, so you can correlate, re-aggregate, or trace an item back to the envelope it came from.