Related link: http://www.informationweek.com/story/IWK20030205S0007
The Big 3 Web Services players are Microsoft, IBM, and Oracle, according to this InformationWeek article and Gartner Research. “In 2003, most systems integrators will turn to Microsoft .Net, IBM WebSphere, and Oracle. In September 2002, Gartner wrapped up a survey of 44 consulting and systems-integration vendors in North America. Microsoft .Net was targeted by 58% of the systems integrators as one of the top three Web-services products to ramp up delivery capability, according to Cantara. IBM’s WebSphere garnered 40% and Oracle came in third at 31%. Sun, Cantara said, was a strong fourth.”
Sun is indeed fourth as it integrates WS-I with Java 2EE 1.4. Enterprise Java developers will be allowed to develop, integrate, and deploy Java 2EE API like EJB along with Web services specifications such as WSDL and UDDI. BEA Systems should be fifth. Both Sun and BEA have also developed a sophisticated meta tag method for allowing Web services and JSP developers to use tags to build enterprise applications using or incorporating complex enterprise Java API (i.e., EJB, JMX, etc.). Sun’s JCP has several JSR’s on this while BEA is already implementing this in its WebLogic Studio IDE in the form of JWS (Java Web Services) Tags. JWS has been around for nearly a year, and could be the reason that BEA went with WebLogic Studio (formerly Cajun) over WebGain Studio (formerly Visual Cafe).
Sun and BEA are still major players that could at least give Oracle some problems. They both have the tools to compete with Oracle. IBM still has the cash. Also, IBM along with Microsoft will always take the lead in Web services given that these two companies have been the innovators and driving forces behind most of the Web services specifications we see from the W3C and others, including SOAP.
Microsoft’s .Net and the IBM-Oracle-Sun-BEA support for Java based Web services can be best described in terms of market support by the following: “Large companies, which are more likely to have mainframe legacy applications, are turning to Java/J2EE to layer on Web services atop the infrastructure. Java is more popular in large-scale activities such as enterprise resource planning, Cantara notes. Smaller companies, which can start with a clean slate, more or less, find .Net more attractive and are most likely to use it for Web services related to E-commerce.” Of course, whether it’s .Net or Java flavor, Web services are still based on XML. It’s just a matter of preference regarding the infrastructure that’s already in place, comfort level, and costs.
What do you think of this research. Do you prefer .Net or Java? Would you use both?