midSOA
Explain the 'Canonical Data Model' pattern.
Updated Apr 28, 2026
Short answer
A standardized data format used for communication between services to avoid custom translations.
Deep explanation
Mid-level SOA design involves managing the lifecycle and interaction patterns of services. Statelessness is key for load balancing, while abstraction ensures that consumers don't break when the backend database is upgraded. ESBs play a critical role here in mediating between modern REST clients and legacy SOAP backends.
Real-world example
A retail system using BPEL to orchestrate an 'Order' process involving Inventory, Payment, and Shipping services.
Common mistakes
- Hard-coding service locations instead of using a registry or ESB abstraction.
Follow-up questions
- What is MTOM?