"I’ve looked at clouds from both sides nowOr, as Larry Ellison put it more succinctly, "What The Hell Is Cloud Computing?"
From up and down, and still somehow
It’s cloud illusions I recall
I really don’t know clouds at all”
Like all things Web 2.0, there's an overabundance of fascination with what can be done vs. how fast it can be done or how many things can be done, before the system might fail to scale.
Excerpted YouTube video: In this interview at the CMG 2008 conference, TeamQuest's director of product management, Scott Adams, and I discuss this oft-overlooked aspect of the cloud-computing hype and reflect on what is really needed for better performance and capacity management. My CMG papers on performance management requirements for virtualized services (referred to during the interview) are:
- "The Virtualization Spectrum from Hyperthreads to GRIDs," CMG 2006 (PDF):
- "Visualizing Virtualization," CMG MeasureIT 2007 (HTML).
For better cloud performance and capacity management, we need more whistles and fewer bells.Update: Lest I may have left the impression here that I am somehow anti-cloud (which is not true), take a look at a my remarks on an early and very impressive cloud-based GIS application of Amazon's EC2, thrown together in a very short time (24-48 hrs?) to search for the late Jim Gray; then missing at sea. Google provided thousands of satellite images, but only Amazon was able to load them quickly into a relational database and front-ended it with their Mechanical Turk interface for literally thousands (perhaps millions) of eyeballs to scan for Gray's yacht. I think this is a remarkable application of cloud technology, which could not have been done in any other way as effectively and efficiently. It also performed well. Moreover, since Amazon runs a real business on such highly distributed systems, it was in a superior position to implement this app in short order. They deserve a lot more kudos than they seemed to get publicly for pulling it off.