Transformation
Shaping message content at the edges so the bus always carries clean canonical data.
Transformation patterns convert external formats into the canonical model on the way in and back out on the way out, and adjust payloads in between. The normalizer and canonical data model are the backbone; the enricher, filter, claim check, and envelope wrapper handle the rest.
Normalizer. Convert each incoming format into one shared canonical message with a per-source receive map.
Canonical data model. One internal schema per business entity that every integration speaks.
Content enricher. Add data a message is missing by looking it up and merging it in.
Content filter. Strip a canonical message down to just the fields a destination should receive.
Claim check. Keep a large payload out of the message body, carrying only a reference token.
Envelope wrap / unwrap. Add or remove the protocol envelope a system expects around the payload.