Mamoon Yunus, of Forum Systems and Cross-Check Networks, makes the point that XML Gateways are often under-utilized.
We have deployed WS-SOA Gateways at many locations worldwide, and most of the deployments are 1-u Appliances with dual CPUs and crypto accelerators. Most of the load requirements center around message sizes. I have yet to see a deployment that comes close to harnessing the 1000-2000 TPS capacity of appliances when small to mid size documents are invovled ranging from 1K-100K.
http://soa-testing.blogspot.com/2006/10/load-testing-web-services.html
He goes on to say that there certainly are organizations sending some very large (>20MB) XML messages, but not so many sending large volumes of smaller XML messages.
I'd agree up to a point. Here at Vordel, we've also seen some B2B partner-integration rollouts where TPS volumes are not large, since the traffic is consistent, not bursty. We've also seen the "huge messages, low numbers" scenario, and in that scenario we used message-queuing to avoid overloading the recipient system. And, most internal SOAs start out with a small number of Web Services [a notable exception is SAP-based SOA's, where the large number of service-enabled ABAP interfaces can create a "big bang" effect].
But, the area where we have seen high TPS volumes is telecoms, specifically mobile telecoms. Text broadcasts of news and sports events [sourced from third-parties via XML feeds], events such as New Years Day, text-based special offer broadcasts - these all involve large bursts of XML traffic through a mobile telecoms Service Delivery Platform. Telecoms is where the high-volume XML traffic is.
12:15:13 PM 
|
