Back to Catalog
Integration
Message Transformation
Message Translator
Convert a message from one format to another — the messaging equivalent of the Adapter pattern.
Intent & Description
Real-world Use Case
Legacy ERP sends SOAP/XML inventory updates. Modern microservices consume JSON events. Message Translator sits between them — converts XML InventoryUpdate to JSON InventoryChanged events. Neither system knows the other exists.
Source
📌 TL;DR
Message Translator = format adapter for your messages. Source format in, target format out. Neither end knows the other’s schema. Essential for legacy-modern integration.
Advantages
- Neither system needs to change their native format
- Centralized translation logic — one place to update when schemas evolve
- Enables integration of legacy and modern systems
- Reusable translation components across integration flows
Disadvantages
- Translation logic must be maintained as source/target schemas evolve
- Semantic loss possible if source/target models do not map cleanly
- Translation adds processing overhead and latency
- Complex translations can become brittle maintenance liabilities