Receive a message in the producer's structure or envelope.
Message Transformation
Normalizer
Route each incoming format through the appropriate translator and produce one normalized representation for downstream processing.
How do you process messages that are semantically equivalent, but arrive in a different format?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 Normalizer works
The message representation changes while its business meaning is preserved or enhanced.
Source format
Normalizer
Target format
Apply Normalizer to reshape, enrich, wrap or normalize the content.
Deliver a representation that the receiving system can understand.
What this pattern helps you decide
Route each incoming format through the appropriate translator and produce one normalized representation for downstream processing.
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
- APIM content-type normalization
- Logic Apps schema-specific mappings
- BizTalk maps into a canonical schema
How the analyzers can surface it
- Multiple source schemas converging to one model
- Adapter-specific transforms
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.