SOA Tips-Be aware of SOAP Verbosity (Message size overhead)28 Apr 2007
Depending on the nesting levels of the parameter types, XML and SOAP message overhead can grow significantly. As I mentioned in previous blog entries, document/literal always performs much better than other style/use models. Keep in mind that XML data cannot be optimized too much. When using SOAP, the SOAP envelope has to be extracted, the XML information that it contains has to be parsed. SOAP requires type information in every SOAP message. Due to the XML character-set restrictions, binary data when included in XML bloats the payload, and when converted to a base64 encoded message also requires encoding at the sender’s end before packaging the document and decoding at the receivers end before parsing the XML payload. You just have to be aware of these issues.