Open-source application stacks -- and the scramble to build, support and sell them to enterprise IT customers -- have been one of the technology industry's hottest trends this year.
Vendors hawking them include the likes of Hewlett-Packard and IBM, Linux purveyors Red Hat and Novell, and independent support providers such as SpikeSource, OpenLogic, SourceLabs and many others.
Yet a growing number of critics say that stacks has already become a hyped-up buzzword that fails to serve many users.
"Stacks are rigid and deterministic," said Winston Damarillo, CEO of Simula Labs, a open-source software provider. They are "prefab solutions, which most customers don't really want in the first place."
Take Davis Tharayil, CIO at US-based Home Insurance, for example. Tharayil is looking for a cheaper alternative to the Oracle databases on Solaris servers the in-liquidation insurer runs now. Tharayil is testing a custom server appliance built by rPath with the open-source Ingres database running on a stripped-down version of Linux. Even though Tharayil was looking for a plug-and-play product, at no point did he consider a precertified open-source application stack.
"A full stack just wasn't necessary," Tharayil said. Besides, he added, "I've been in the business for 35 years. Every time something new comes along, they say it's a silver bullet. And I still haven't found one."
Application stacks have a long history in the proprietary software arena. Vendors such as Microsoft and Oracle have long marketed their integrated product line to customers as a way to boost interoperability and cut costs, though critics say that also leads to customers facing vendor lock-in.
In open source, most software providers remain small, offering at most a handful of applications rather than entire lineups. That put the responsibility on corporate users, or their highly paid consultants, to ensure that the software worked together -- something that could easily wipe out the savings from using free software.
The first true open-source stack emerged during the dot-com boom in the form of Web servers. Dubbed LAMP, it included the Linux operating system with the Apache HTTP Web server and MySQL database on top, supported by code written in languages such as Perl, Python or PHP. LAMP's popularity woke up vendors to the potential of packaging and testing open-source applications in a tidy way, cutting deployment time and risks for companies, especially smaller ones.
That has led to the emergence of dozens of LAMP imitators, as well as open-source software stacks running on Windows, dubbed WAMP. Critics call it a flood of poorly tested, not-very-well-integrated stacks.
"When you try to certify everything from soup to nuts, it ends up not meaning much at all," said Erik Troan, chief technology officer at rPath.
Others said that despite the apparent bounty of open-source stacks, they don't begin to meet the particular needs of many companies. "Many open source stack providers can only afford to support the most popular open source components. There are so many open source projects that no single vendor can assemble the expertise to meet every customer need," declared The 451 Group in an August report critical of open-source stack providers.