What it is
A message translator converts a message from the format one system speaks into the format another expects. It is the integration equivalent of an adapter, bridging differences in data model and structure.
How it works
- The translator reads an incoming message.
- It maps fields, renames keys, and reshapes structure.
- It emits a message the receiver understands.
Why it matters
- Lets systems with different schemas cooperate without changing either one.
- Isolates format knowledge in one component, not scattered across services.
- Supports layered translation: data types, structures, and even transport.
Translators range from simple field renames to complex transformations across encodings. Keeping translation separate from routing and business logic keeps each piece clear. A translator that does too much becomes hard to maintain, so complex mappings are sometimes split into a chain of smaller translators, each handling one level of difference.
Key idea
A message translator reshapes a message from the sender format into the receiver format, isolating schema differences in one place.