Microsoft's Connected Systems Division released the results of a benchmark study that showed that applications based on WCF Web services outperformed J2EE applications running on WebSphere (ver 6.1.07) by as much as whopping 285 percent! Woah! From a cost point of view, the .NET solution is supposed to be one-fifth of the IBM Java solution. For the study four core tests were benchmarked, namely:
- Web Services: Remote activation of back-end services from the front-end Web application.
- Durable Messaging: Orders placed via transacted/durable queue in loosely-coupled architecture.
- Non-Durable Messaging: Orders placed via a non-durable/non-transacted queue.
- Monolithic: All elements of application run in a single JVM or CLR instance, no Web Services or messaging. In this mode, orders were set to be placed synchronously.
Of course, given this is released by Microsoft there will be some bit of skepticism, but feel free to check out the details (PDF) – 10.3 mb and 92 pages of both the study and the results.
Similar posts to check out:
- May 19, 2012 -- Metro Apps in C++ anyone? (0)
In Visual Studio “11” when I try and create a new C++ Metro app using the built-in template, I get the following error: “Can’t find localized resources”. I wonder if anyone else has managed to get around this? I am running the Consumer Preview Build of Win 8 (Build 8250). ... - April 25, 2012 -- SkyDrive, Windows 8 and Domain Account (0)
I am running Windows 8 on my primary work machine now, which is domain joined. When I try and use the SkyDrive metro app (which ships with Windows 8), it does not like that fact I am domain joined and wants me to switch accounts, which is something I don’t want to do. This of course works great for those who are not domain joined and essentially are personal machines. For many of us who will be using this on ‘work’ machines, this seems like we will be ignored. Of course I can install the deskt... - March 6, 2012 -- Enabling Win 8 Metro on a Netbook (0)
When you install Win 8 on a Netbook the screen resolution would be too low for Metro apps to run which is a bummer. One way to get around this and “fix” this is to update the registry (and you thought that was so XP!) :). Run Regedit and search for “display1_downscalingsupported” (without quotes). Find all occurrences of this entry and change its value from 0 to 1. Reboot when finished and you should have more options on your Screen Resolution choosing which will allow you to run Metro. :) ...
Tags: .microsoft
