Utilities as models of business efficiency? I dont think so. I tend to associate utilities—especially electric companies—with bright yellow, extended-cab pickup trucks emblazoned with a Mass. Electric logo parked in front of coffee shops. That and promises of nuclear power too cheap to meter and some long-ago high-school physics class where I learned that about 30 percent of the power generated is lost getting it to the house. Then there was that business about electrocuting the elephant. Ill get back to that in a minute.
So computer vendors will have to forgive me for not getting as breathless as they do when theyre talking about the new world of computing based on the utility model. IBM is the most vocal champion of this with its on-demand computing initiative.
Hewlett-Packard, meanwhile, claims to be the latest advocate, as well as the first proponent, of the concept. Recently, HP announced the name "Adaptive Enterprise" to package the idea. In both cases, users are urged to plug into the computing cloud not just to exchange data but also to tap into applications. A similar notion is behind Suns N1 scheme. The vendors all assert that utility computing is stable, safe and efficient. While lacking a claim to first usage, we as a publication (then PC Week) carried an article on computing fabrics in 1998. That article was written by Erick and Linda von Schweber, who called themselves the Infomaniacs and were well-remembered at Comdexs Spencer Katt parties for their glittering robes and out-there predictions. When I talked to them earlier this month at their new digs in San Francisco, they were still well-grounded in fabrics, grids and the utility computing business.
While the fabrics are still being woven, in Infomaniac speak, the days when utility computing will be easy and safe are still about a year and a half away. Thats not too far for planning purposes, but its still not reality, either. According to Erick von Schweber, the payoff in utility computing will be when functionalities can be combined while the methodologies to build those functions remain constant.
That view was echoed by John Jordan, principal in the office of the CTO, Cap Gemini Ernst & Young Americas region. "Were suggesting clients work on architectural fundamentals so their code base, network, application semantics and other elements will be ready for Web services, grids or utilities," said Jordan.