The Keene View on Web 2.0, Ajax and SaaS

With all the excitement around Java alternatives like Rails, a much more important and less commented upon migration has been occurring

For ten years, the ponderous J2EE standard has made the lives of Java programmers everywhere miserable. While various Java standards committees considered gravely what to do next, corporations have been steadily moving to .NET.

In our market research for WaveMaker, we have found that a over 30% of the corporate IT market has moved from Java to .NET. As with many other Microsoft technologies (SQL Server comes to mind), Microsoft has gone from having a laughable solution to getting the last laugh.

We have also found a surprising number of Java developers who tell us that the complexity of J2EE and the difficulty of finding experienced Java developers is forcing them to embrace .NET despite their loathing of all things Microsoft.

Spring and WaveMaker are two companies addressing the core problems underlying this market shift. Spring is the application server that J2EE should have been – lightweight and powerful. WaveMaker is the visual development platform J2EE never had.

Together, Spring and WaveMaker offer a compelling and highly productive alternative to .NET.

How compelling? One of our Fortune 500 customers built the same application (57 web pages, 28 database tables) in both .NET and WaveMaker. The app built with WaveMaker was completed with one third the man-hours and 98% less code (more on this in a later post).

The conclusion is stark - either the Java and open source community needs to put good productivity solutions in the hands of corporate customers, or the data center will go the way of the desktop.

Labels: j2ee, ruby on rails, spring, WaveMaker

Ben Worthen of the WSJ recently posted an entry about Web 2.0 adoption. He sited a Forrester survey that concluded Enterprise Web 2.0 solutions would gain broad adoption in 2008 despite clear CIO resistance to the siren call of blogs and wikis.

As a strong proponent of Web 2.0 in the enterprise, we at WaveMaker want very much to see a rapid adoption of these technologies at the corporate level. On the other hand, wishing won't make it so - the grab-bag of technologies and ideas that constitute Web 2.0 are bound to confuse the IT community.

There are two possible observations here:

1. Damn the data, full speed ahead. Just like drug companies that sink a great deal of money into disappointing clinical trials that they then attempt to spin into medical break-throughs, analyst firms like Forrester won’t sell many copies of a Web 2.0 report that concludes Web 2.0 ain’t happening in the enterprise anytime soon. Thus there is a strong incentive for the report authors to refute their own data in the survey summary.
2. Web 2.0 is being pulled into the enterprise, not pushed. Since the PC, all client-side technologies have been pulled into the enterprise by business users, not pushed into the enterprise by central IT. The main themes of Web 2.0 – rich interface, collaboration and user-driven content – have more to do with how users interact with their computers than with computer infrastructure.

At my WebGuild panel this week, Rod Johnson of SpringSource observed that open source technologies like Spring and WaveMaker build unstoppable momentum within the IT organization by solving fundamental problems that much bigger players either cannot or will not solve.

For Spring, the tailwind came the intractable complexity of the EJB standard that left developers desperate for a simpler, more lightweight java application server. For WaveMaker, the tailwind comes from the complete dearth of visual tools for web development that would enable MS Access, Lotus Notes and PowerBuilder developers to come out of the client/server dark ages and build the kinds of web-based applications that their end users want.

Labels: access, powerbuilder, spring, WaveMaker