Caching was not allowed in this benchmark
I think because it would make .NET look bad.
m$ wouldn't allow the results to be published
if they weren't the best.
Read the windows EULA.
They indicate in the report that they understand that Web services are a facade to the underlying business process transaction, but then measure the totality of the system, rather than just the Web services layer.
It is an interesting report because it tends to imply that if you move to a proprietary system, you get better results. Or conforming to open standards causes performance problems?
I was thinking of letting things lie with this topic. But I have to be fair. Benchmarking can be made to justify any particular spin someone wants to deliver. However, in the enterprise world that .NET and J2EE live in, there are factors that lie beyond the manufactured realm a benchmark can conjure. Connectivity with business IT policy, interaction with legacy systems, operation in a distributed environment and security are some of the challenging issues. And certain approaches are going to yield better results for one technology over the other.
Web services are going to be one part of the business integration puzzle. But Web services are not producers of data, they are connection and transport services for accessing data. Data producers will in most businesses, still be the ERP and legacy systems that automate and perform the business processes. They will ultimately determine how fast you can transport data through web services, and the manner in which data is consumed will determine how fast and how much data you must actually deliver. If a particular company were to generate the number of bills represented by the transactions in the report, then that would be a good problem to have.