Search My Blog & Website
Wednesday, November 05, 2008
XML's role to SOA
SOA leverages the standard XML data representation to reduce underlying complexity of application environments. Some are examples are;
- Passing XML documents and schemas between applications allows for the standardization of data format and type, which this improves predictability and performance.
- XML documents are easily understood by different stakeholders such as architects, analysts, developers and users, leading to enhanced data maintenance, traceability and clarity.
- XML allows the support of standardized vocabularies across the enterprise, hence reducing mis-interpretation of corporate data and data models.
- XML allows a SOA based system to realize a foundation data representation and data management layer.
For SOA to leverage the benefits of XML, a solid XML architecture should be developed and implemented. Such architecture should include architectural components for data transport, structure, validation, verification and modeling. Accommodations for RPC-style messaging needs to also be considered if an environment does not support document-style messaging (SOAP). In such cases we need to ensure no conflicts exist between usage of RPC-style SOAP messages (from shaping XML documents around a parameter data exchange model).
- Passing XML documents and schemas between applications allows for the standardization of data format and type, which this improves predictability and performance.
- XML documents are easily understood by different stakeholders such as architects, analysts, developers and users, leading to enhanced data maintenance, traceability and clarity.
- XML allows the support of standardized vocabularies across the enterprise, hence reducing mis-interpretation of corporate data and data models.
- XML allows a SOA based system to realize a foundation data representation and data management layer.
For SOA to leverage the benefits of XML, a solid XML architecture should be developed and implemented. Such architecture should include architectural components for data transport, structure, validation, verification and modeling. Accommodations for RPC-style messaging needs to also be considered if an environment does not support document-style messaging (SOAP). In such cases we need to ensure no conflicts exist between usage of RPC-style SOAP messages (from shaping XML documents around a parameter data exchange model).
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment