10 items | 3 visits
Rajan Desai's List: Architecture and Design
-
-
-
-
-
When I first saw SOAP, I pretty much saw it through the eyes that XML-RPC had trained - as a more powerful mechanism for accessing APIs through Remote Procedure Calls (RPC). While I have some fondness for XML-RPC when used in relatively simple and small environments, I have deep qualms about using RPC in general on any large scale over any long period of time. RPC is brittle, breakable, etc. - we've been over that before.
-
Loose coupling is central to the nature of Web services-based application integration. That's why it seems to me that the right model for XML in Web services is a message-oriented, document-based one rather than one based on remote procedure calls.
-
-
-
-
-
Some guidelines that can help you identify which mode to use in a particular scenario are:
* Some XML is intended to be treated as documents (for instance, consider a newsfeed). Document style should be used when the message payload is going to be processed as XML, for example, when it is to be transformed into another format and stored directly into a database or if the payload is going to be merged with other XML and then sent on to another destination.
* If your application already has XML interfaces, you will probably want to use document style. Likewise, if you are sending data conforming to an industry XML vocabulary, you will probably to want to use document style.
* When executing functions or sending data which will be analyzed, you need to carefully evaluate the choice between document and. RPC offers simplicity and sometimes better tooling support. Document offers greater flexibility and decoupling, and under some circumstances (large messages with many elements) vast reduction in message size, but may requires more XML expertise and hand coding.
-
-
1 - 10 of 10
20 items/page
List Comments
(0)
List Info