Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Strategies & Market Trends : Gorilla and King Portfolio Candidates -- Ignore unavailable to you. Want to Upgrade?

To: stockman_scott who wrote (53426)	1/14/2003 4:21:07 PM
From: Thomas Mercer-Hursh	Read Replies (3) \| Respond to of 54805

When I saw the reference to Slow Boat, it brought to mind this recent post on a technical list I subscribe to. Well, unfortunately that is an issue that needs to be taken into account when working with web services based on SOAP, being the main problem the amount of time needed for serializing/deserializing data sent thru the wire (I mean the process of creating an XML SOAP valid structure). Unfortunately, SOAP (as a protocol) trades-off performance to be easy-to-use. I had the chance to compare Microsoft .NET web services + a clasic COM app and the readings were not promising : I was able to call a method residing in a COM object 500 times in one minute but just 50 calls for a .NET web service (both of them doing the same thing), when comparing .NET and Java, I was able to perform 50 calls (.NET) in one minute against 36 when using Java. If we are talking about performance, nothing beats CORBA :-) (but again... the trade-off is performance vs being easy-to-use) Recapping: 500/min COM ("old-fashioned" direct connection) 50/min .NET web services 36/min J2EE web services Not too promising, actually, at least not for high performance applications.