After a short period of no posts, I am back to the list...
41. More Web Service Deployments A recent survey shows that 53.3% of webservices implementations are done on J2EE as compared to a dismal 33.7% on the .NET platform. This given the fact that .NET is supposed to be a platform designed and tuned for webservices.
Well this survey is based on a population of 1000 people and in the end they do conclude by saying use whichever platform you are comfortable with. Lets accept the facts. MS was in WS much before Sun. Java would have been in trouble with WS if not for IBM. So this I think is not an argument at all
42, Sophisticated Logging via Log4J
.NET's inbuilt support for loggin is very good. Apart from that there is an opensource project called Log4Net that provides Log4J like functionalities
43. Distributed Caching There are multiple vendors and open source projects that provide distributed caching (i.e. SpiritCache, Coherence, Gemstone, JCS, Oracle). Distributed Caching solutions are unavailable in .NET. In fact "Centralized Caching" for .NET is in one site's wishlist.
This is something I don't know enough about to comment.
44. More Alternative Messaging Implementations There are more messaging implementations that are supported in Java, furthermore, they are supported by a standard API (i.e. JMS). What this means is that you can choose the best messaging product for your situation. For example, Tibco is used for high demand financial markets, iBus supports wireless environments, Sonic can bridge Mail and FTP messaging. With .NET you only have one choice, however, there are JMS vendors that can also bridge to .NET.
As far I know most of the product vendors do support COM equivalents for their libraries. So I don't think this is in favour of Java except for may be the single interface, JMS part. Since I don't use messaging much in my day to day applications, I cannot really expand on this one though.
45. Write Stored Procedures and Embedded SQL in Java You can write Stored Procedures in Java for Oracle, DB2 and Sybase to name a few. Java has a standard way of embedding SQL called SQLJ, which is supported by Oracle, DB2, Sybase and Informix . In the .NET environment you write a stored procedure using TSQL, which doesn't look anything like C# or VB.NET!
Point conceded. But AFAIK, SQLJ has not been very sucessful. Some people use it but the majority still stick to PSQL or TSQL or equivalents. Anyway the next version of SQL server does have CLR integration and things may change then
.net vs java the debate will be never ended, but I know one thing i.e. there is every thing for every one.
Posted by: Sam | March 14, 2012 at 09:41 AM