But, it's the latest tech word-soup. Like in 2005 when everything Javascript became "Ajax", everything distributed becomes "Cloud".
I was hugely skeptical of the cloud concept -- sneered at it, even -- until i started doing the cost/benefit analysis.
But then some marketer somewhere (I'm guessing Salesforce, but that's my own bias :) decided that any web application could call itself "Cloud" (since "Software as a Service" was no longer cool. Again, I'm blaming Salesforce for flogging that horse to death...). This way, even normal people can use the cloud/buy cloud services, and it's just as easy as using the Web since it's really just the Web! (Way to go, smart and savvy Internet^H^H^H^H^H^H^HCloud user—you're so much smarter than everyone else and can expect to get promoted over/laid more than your coworkers still using that ancient Web 2.0!)
The Wikipedia article on Cloud Computing is a good illustration on how vague the term has gotten, especially how ill-defined all of the sub-classes are: Platform as a Service, Application as a Service, Service as a Service. Pretty much anything on the Web can be made into a definition of "cloud" somehow.
I'd really like to see Cloud Computing only applied to things involving immense elastically scalable computing and storage that can be provisioned and taken offline immediately, but I don't think that's going to happen. The meaningfulness of the term has been destroyed by the rampant "me-too"-ing of the industry.
The field developed and it became useful to distinguish between different uses of Javascript, so new names were invented to do that.
Javascript that changes the page and calculates on user input is still 'Javascript'. Javascript that sends requests to a server and updates the page based on the result became 'ajax', Javascript that does processing in a small-tool-page-independant fashion became 'bookmarklets', Javascript that does page processing in an after-market-modification fashion became 'userscripts'.
Likewise distributed computing - that just refers to using multiple computers. They could be yours, rented, local, remote, clustured, desktops, servers, using any kind of framework. Cloud computing refers generally to renting remote servers from a third party who provide a particular software stack and interface and a restricted set of services. Yes the edges blur, but having 5 linodes to store data on is not really cloud computing, it's just renting servers, but having an S3 account is.
All our critical business apps are on Google and we can test and scale our software on AWS.
It's funny because the last company I founded (Electric Cloud) was specifically doing distributed computing stuff and we had to buy and install tons of servers just to be able to test our code. Today, founding that company would be totally different... we'd probably buy a few servers for some in house testing of key performance critical elements and then give our credit card to Amazon and buy what we needed as we needed it.
However, the idea of moving code near to the data is a good one since moving data tends to be the slow part. But that's hardly a new concept, just look at Teradata.
You say that as if MapReduce is the only thing you can do with Hadoop. It has a key/value datastore too, and since recently a relational database:
It's frustrating, and it actually comforts me that this can happen even to the likes of Larry Ellison.
Mana is something geeks quibble over when their magic missile cast fails.
Manna is magical honey-bread that falls from the sky for true believers.
Which is a funny word to use here, because you just wrote that comment to contradict Ellison's accusation that cloud computing was only for "true believers".
Well played.
It's so easy to sit back on your mega yacht and dismiss cloud as something that's always been around and always will be and blah blah blah, but for a little startup it's MANA FROM HEAVEN.
To be able to do massively compute intensive or storage intensive tasks on demand without sinking a million dollars of capital into a datacenter is the difference between success and failure for my little startup.
How many times have you heard "oh, there's a ten week lead time on that server" or "there's no more power in the cage" or "there are no more cages at the datacenter" or "i'll be up all night recovering the raid array" or any number of other hidden costs in owning or trying to own hardware?
We check our cost projections for buy vs cloud almost every week, and when the time comes we'll definitely buy, but for we couldn't be doing what we're doing without it. Sure it's overhyped, but so was the fucking web. Yes, there's weird performance stuff and not always enough boxes, but so what? Sorry if I'm missing a subtler message he had, but i had to turn off the video after about 30s because it hurt my brain.