Whither Web Services Performance

[Frank Kelly]

The few performance numbers for Java Web Service performance have been pretty good (40+ per second) but are not as good what .Net does.
http://gotdotnet.com/team/compare/Middleware.pdf
(The Middleware co. are notoriously biased however)
Then again neither is close to what MQSeries / Tibco can handle 10,000 + per second.
Do the authors think Web Services will be able to bridge some of that gap especially with the overhead of XML parsing and encryption/decryption and if not how much impact will that have on adoption?
Thanks!
-Frank

[JeanLouis Marechaux]

This IBM article could also help you to compare the Web services performance according to the encoding style used.

[Lasse Koskela]

Well, encoding messages in XML inevitably increases the need for bandwidth and CPU power. However, I don't think this will be a show stopper as the same has happened with a lot of technologies. For example, HTTP is definitely a lot less performant than a number of custom, more specialized communication protocols out there. Yet HTTP is often considered the more appropriate solution--because you get certain things for free (for HTTP, a large installed client base, server software, and so on). With Web Services these things are interoperability etc.

[Ramesh Nagappan]

Originally posted by Frank Kelly:
The few performance numbers for Java Web Service performance have been pretty good (40+ per second) but are not as good what .Net does.
http://gotdotnet.com/team/compare/Middleware.pdf
(The Middleware co. are notoriously biased however)
Then again neither is close to what MQSeries / Tibco can handle 10,000 + per second.
Do the authors think Web Services will be able to bridge some of that gap especially with the overhead of XML parsing and encryption/decryption and if not how much impact will that have on adoption?
Thanks!
-Frank

Adding facts, first you maust understand "Web services" is not an alternative to MQSeries or TIBCO. Web services is all about standards and standards based communication where disparate application can interoperate and interact each other.
In aspects of performance, it depends on what are you aiming at ! Web services performance can be measured in many ways but it is "Text based Protocol", so it is expensive in bandwidth usage than "binary" based protocol. But the advantages are tremendous....
But still, I have seen some good Web services performance numbers...take a look at "www.pushtotest.com".