DevX spoke with six of these vendors to get an overview of this next frontier of AJAX development:
- Backbase makers of Backbase enterprise AJAX software
- Helmi Technologies makers of the Helmi Open Source RIA Platform
- ICESoft Technologies makers of ICEFaces, a Java EE framework for AJAX applications based on JavaServer Faces
- JackBe makers of the enterprise AJAX development and runtime environment, NQ Suite, and the Presto rich enterprise application platform
- Nexaweb makers of the Enterprise Web 2.0 Suite of products for Java-based AJAX development
- TIBCO General Interface makers of General Interface (GI) toolkit for building desktop application-like Web applications
Robert Lepack, VP of marketing for ICESoft, gave a break down of what enterprise customers are looking for, which seemed to ring true for the market as a whole. He said ICESoft clients are divided evenly between those migrating legacy apps to the Web and those building new RIAs. He also detailed their evaluation criteria when selecting an AJAX solution: richness of the component libraries, SOA compatibility, standard tools support, and portal integration.
|There's a difference between 'AJAXified' pages and AJAX/rich Internet applications for the enterprise.Kevin Hakman, director of product marketing for General Interface|
Helmi Technologies Founder Juho Risku said, "Enterprises are basically looking for savings because of the instantaneous user experience on enterprise applications. That's the reasoning behind AJAX [deployments]." He gave the example of an enterprise application handling 500 clicks per user, per day and taking five seconds to respond to each click. With 1,000 users, that adds up to millions of seconds per year those users spend waiting.
"There's a difference between 'AJAXified' pages and AJAX/rich Internet applications for the enterprise," said Kevin Hakman, director of product marketing for General Interface. As an example, he cited H&R Block, which annually sets up 12,000 additional offices during tax season and equips them with high-productivity GI workspaces through the browser.
The vendors made it clear that AJAX isn't right for every application. Nexaweb CTO and Founder Coach Wei said, "AJAX is a great technology for enhancing the performance functionality of Web-based applications in the browser [but it] is not good for much more client-centric applications [such as] the traditional PowerBuilder kind of application."
|Anything that requires signal processing or complex algorithms on the client side is definitely not something AJAX should be used for.Helmi Technologies Founder Juho Risku|
"Any ERP application, that's perfectly OK with AJAX," explained Risku, but he stipulated, "Anything that requires signal processing or complex algorithms on the client side is definitely not something AJAX should be used for."
So does that mean AJAX applications won't scale well?
JackBe CTO John Crupi offered a different perspective, as his product is an SOA service consumer. "The front end will be AJAX, but ultimately if you really want to get the performance and scalability you need for enterprise apps, you have to have a framework that extends into the backend enterprise. In our view, that backend extension is using SOA as the data service provider," he said.
Adding to the complexity is the fact that AJAX development currently lacks standards. This is an issue all six of the companies DevX spoke with (and some 49 others) are trying to address collectively through the Open AJAX Alliance, an industry body whose mission is promoting interoperability among the multitude of AJAX widgets, components, and libraries.
"The Open AJAX Alliance is taking all of the vendors and saying 'Let's not fragment the market the way Web service standards bodies did and have competing standards,'" said Crupi. "The first step is to support interoperability. You should be able to intermix various widgets and frameworks and not have a problem."
Backbase chief Pleiter also advocates for a single common API that can serve as a basic language specification for all AJAX solution vendors. As he sees it, even if all the different AJAX implementations could cooperate, each would still have its own API. He said, "We now have 200 different APIs for 200 different check problems, which is clearly way too fragmented [and] clearly doesn't drive for any standardization."
|A flurry of open source activity has occurred in the AJAX market.|
Today, many of the vendors' products already support widely used open source toolkits such as Dojo and DWR as interoperable add-ons to their native libraries. A majority of the companies DevX spoke with have even released their own products as open source projects. In just the past few months, a flurry of open source activity has occurred in the AJAX market:
Although the vast majority of freely available frameworks, toolkits, and libraries on the AJAX landscapeHelmi estimates 1,500 in allaren't involved in the interoperability effort, most of the vendors feel confident that the ones that matter are. Hakman predicted that fewer than 10 would emerge as broadly adopted, and Pleiter said, "I think 80 percent of the stuff doesn't even qualify to remain in the marketplace because it's just a small fragment, it's just a piece of code. They are not viable options, especially in the enterprise."
Helmi Founder Risku added, "Most of the platforms are such that no one even knows that they are there. There definitely will be a lot of consolidation happening."
If the Open AJAX Alliance is successful, however, Hakman sees the Java platform as a model of what AJAX could become. "Like in Java with JSP, Swing, and Spring, you've got a different tool for different tasks within that context. The idea is [that] AJAX is just an ecosystem with a number of large frameworks and toolkits that are broadly adopted, but plenty of room for more [vendors] that make specialized widgets."