Two Camps: Microsoft .NET and Java

Remember that Web services have been designed to enable applications to work with other applications over the Internet regardless of what operating system and program languages each application has been written in. This being the case, it should matter little which application server platform you build your Web services applications upon. The whole point of Web services is to enable whatever platform you choose and whatever language you use to work with other, different systems and languages.

As things stand now, there are two competing approaches to building Web services applications and that's okay (for consumers and business buyers, choice is a good thing). One approach involves using a Microsoft product suite and the C# language environment on Intel-based platforms, while the other involves using platforms made by Sun, IBM, Hewlett-Packard, Compaq, and other suppliers running the Java programming language.

What are the dynamics of this Sun Java (more specifically Java 2 Enterprise Edition J2EE) versus Microsoft .NET battle? Is one better than the other? Is one going to dominate the other? From an IT buyer perspective you need to consider that both architectures can get you where you're going from an "application interoperability" point of view. The real story has nothing to do with which approach is better it has to do with the motives of Sun (and other Java backers like IBM, HP, and Oracle) versus those of Microsoft.

The J2EE versus .NET Rivalry

The big picture in this rivalry looks something like this:

• It is commonly believed that he who controls the application development environment will be able to capture the hearts and minds of ISV and custom application developers.

• Getting developers committed to building applications using a particular vendor's tools and platform creates a high likelihood that they will not switch platforms or application development environment.

• By ensuring that developers are thus "locked in," vendors increase the probability that their particular systems and development environment will be purchased in the future.

In other words, it is commonly believed that whichever vendor wins the battle of "easy-to-use" development tools, utilities, and add-ons (like automated business process management or personalization) will ultimately sell the most software and (in some cases) related hardware. This "Java versus .NET" battle is really about capturing the commitment of developers to a particular way of developing applications in order to lock in future sales. Vendors compete by offering integrated solutions that include systems software (like operating environments and systems management), application development environments, and in some cases related systems hardware, and professional services.