A splitter pattern is used when a batch of messages is received and you need to process them individually. With this pattern you can process such a message by splitting it into small messages. Imagine you have a large message containing multiple orders by different stores and you want to separate each order from each store into a single message, then this pattern can be a fit-for-purpose.
There are different ways to implement this pattern in BizTalk, such as using a pipeline or an orchestration using maps, XSLT, and XPath. As there are multiple ways to implement this pattern, it is good to know what the pros and cons are of each implementation. Envelope debatching or Receive port pipeline debatching is fast, very fast, and suitable for the message only scenarios. The drawback of using this implementation is that when something fails in the pipeline then the entire message fails, so it has less flexibility. This can be resolved enabling the recoverable interchange...