Slashdot Mirror
Multiple Experts Try Defining "Cloud Computing"
jg21 writes "Even though IBM's Irving Wladawsky Berger reports a leading analyst as having said recently that 'There is a clear consensus that there is no real consensus on what cloud computing is,' here are no fewer than twenty attempts at a definition of the infrastructural paradigm shift that is sweeping across the Enterprise IT world — some of them really quite good. From the article: 'Cloud computing is...the user-friendly version of grid computing.' (Trevor Doerksen) and 'Cloud computing really is accessing resources and services needed to perform functions with dynamically changing needs. An application or service developer requests access from the cloud rather than a specific endpoint or named resource.' (Kevin Hartig)"
... is mainly water vapor.
Ok, unless we speak about software, where is mainly vapor ware.
buzzword-compliant computing. I hate stories like this, which are really just cover for somebody's marketing.
Dog is my co-pilot.
Cloud computing is a privacy destroyer. That's my definition.
Take Nobody's Word For It.
Gives Wired and other mags yet another buzzword topic to claim is newfangled and great when really it's just a new paint job on an idea that has been around for decades. But no, really, it's a paradigm shift, we SWEAAAR. Bleh.
I do not respond to cowards. Especially anonymous ones.
What is Cloud Computing - Video
Summary -
"At the Web 2.0 Expo, we asked Tim O'Reilly, Dan Farber, Matt Mullenweg, Jay Cross, Brian Solis, Kevin Marks, Steve Gillmor, Jeremy Tanner, Maggie Fox, Tom McGovern, Sam Lawrence, Stowe Boyd, David Tebbutt, Dave McClure, Chris Carfi, Vamshi Krishna and Rod Boothby the same question: "What is Cloud Computing?". Here's what we got. (more)"
http://www.youtube.com/watch?v=6PNuQHUiV3Q
It's obviously the latest Web 2.0 .NET technology-based user-driven blogging paradigm that gives the bloggosphere the synergy for cloud-based dynamic content platforms!
/business-mode
There are mountains to cross for those that are willing.
At least the name does not pretend to be clear.
My pet definition is resources that can be allocated to different departments, divisions, and users as needed rather than the "box-per-department" model that is common now. In other words, as-needed allocation.
Table-ized A.I.
It's interesting that a fairly large number of these guys refer to the term itself as a buzz word.
I think cloud computing is less of a buzz word than most, but I really think that most of these definitions miss the biggest difference: With cloud computing you outsource *all* your hardware. So, any application where you are not physically talking about what software runs on which piece of hardware is cloud computing to me.
MP3 Search Engine
i always thought cloud computing is what happens when a bunch of researchers score really good pot. "i bet we can get more funding if we call it a paradigm shift"
i didn't just miss assembly. i still do.
it's a shame no one gives assembly the respect it deserves.
What ? Me, worry ?
Reminds me of the infrastructure diagrams of corporate LAN's and WAN's back in the 1990's. They would have a diagram of the local network of each site with servers, workstations, routers and firewalls. Then each firewall would be connected to an X.25 cloud (which looked exactly like a big puffy cloud). If it was an internal ID department diagram, then someone would usually add four or more legs and a face or some lightning flashes (then it became an X.25 spider, an X.25 sheep, or an X.25 packet storm).
Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
Assembly? I wish we were so advanced. We have to do all our modeling in real-time. Though there's something terribly satisfying when your final calculations are complete and the giant mousetrap fall atop the little rodent...
Hrm, maybe it's just my background in systems administration, but I thought cloud computing was just an inevitable combination of large scale web hosting with virtualization.
In late 1990's, businesses generally had their own internet server(s) in a colo facility.
In the early 2000's, some companies outsourced their internet infrastructure to managed service providers - other companies built their own in-house data centers to keep up with escalating application requirements.
In the mid 2000's, server sprawl started to impact practically everyone...the first 100 boxes you deploy can be somewhat interesting, but after that... you're entire admin staff (outsourced or not) ends up spending all its time dealing with faults in existing hardware rather than deploying new services...plus electricity/cooling/etc all get more expensive so everyone starts to figure out ways to avoid putting in new boxes. Poof, in comes with virtualization that's actually reliable and actually interesting when it disassociates the virtual machines from worrying about hardware at all and allows them to move from system to system w/o any need for sysadmins to press the "fail over" or "load balance" buttons.
Now, in 2007, smart marketing and product development people at amazon and elsewhere decide they can take over the web hosting industry by heavily commercializing the large virtualization clusters amazon has already deployed...and poof, wrappers to allow developers to create virtual machines and access back end San storage for the clusters are written, along with other stuff that will appeal to anyone who doesn't have a large existing infrastructure..and it's called "cloud computing". To avoid losing out, everyone else says they have their own cloud computing plans/etc...
Now, I guess this is all there and good...but I always thought that what differentiated good hosting facilities from each other was the quality of the admin staff, customer service, defined SLA's and 24/7 emergency response, comprehensive application monitoring, combined with general availability of senior system architects...all of which I don't think amazon/et al have seriously addressed. That means good managed service or web hosting companies can still succeed by either building their own large virtualization clusters and calling them clouds or rebranding and adding value on top of amazon and other cloud providers.
I think you're looking at it from the wrong perspective -- one needs to look at it from the application's perspective, not the system's perspective. The "cloud" represents the resources needed to perform a task -- it's an abstraction used to represent resource acquisition, not resource allocation.
In practice, though, you're pretty close to the truth. Instead of having an allocated set of computers for processing a group's tasks, they can draw from the cloud, which is available to multiple groups. As your computing needs grow, you can have the Cloud take over another computer, which reduces the number of computing resources, but increases the power of the Cloud. This has the advantage of reducing single points of failure, and more efficiently allocating computing resources. Say you start with 100 Macs... as each Mac is subsumed by the MacCloud, the MacCloud grows in strength. Eventually, there can be only one.
Sorry.
"Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
An "infrastructural paradigm shift" that cannot be succinctly described. Or even not-succinctly described. A paradigm shift into the unknown.
Suddenly, this sounds a heckuva lot like the late 90's.
Excuse me, I've gotta go find some VC.
cogito ergo dubito
Cloud computing refers to a cluster computing environment hosted by a single company. This approach is also referred to as "utility computing," and back around 1999 or so, the companies providing these services used to be called "application service providers."
The difference between cloud computing and grid computing, which was all the rage around 2000 (see the academic Globus project) is that grid computing aggregates *widely* heterogeneous computers under different authorities across Internet-scale wide-area networks. A common approach is aggregating universities' computers to form a large-scale cluster. Disadvantages include the fact that you had to program with MPI, communication latencies are high, and there were a lot of authentication issues.
Cloud computing avoids these difficult issues by having a single company host these services for you, and it's typically being done by the big players who can afford to do so (Amazon, Microsoft, Google). Cluster farms are controlled in data centres under one authority. The programmatic interface is simpler, and computation is typically through a fixed paradigm like MapReduce, although there are known SQL-like approaches to run on clusters. Communication through a GigEthernet is typical in a cluster within a data centre.
Is cloud computing a buzzword? Possibly, but then "multi-core," "data centre," and "XML" used to be buzzwords too. Within five years, doing development on a particular vendor's cloud computing infrastructure may be as viable a (specialised) skill as programming for Windows, Linux, or MacOS.
Cloud computing is a buzzword referring to an environment in which all of your enterprise's data and communications resides in another company's servers. The perceived benefit is that your enterprise does not need to have any of its own servers, and thus your IT department does not need to have any engineers.
IT managers love the concept of cloud computing, as the entire IT budget (beyond what is paid to the company that provided the cloud servers) can be used for salaries and perks for IT managers and their cronies.
Because of this aspect of cloud computing, the companies that provide cloud services try to make their perceived cash costs as low as possible (e.g., "free email servers"), and obtain their revenue stream through other means. These other means commonly include advertising to the users of the cloud servers (who constitute a captive audience) and data-mining what should be the enterprise's confidential intellectual property.
Cloud computing service providers are often multinationals, meaning that the data may end up residing in a different country with very different privacy and data confidentiality laws.
As of 2008, the problem of loss of control over intellectual property and the risk of foreign storage is not generally recognized. The small number of engineers and privacy advocates who sound the alarm are regularly dismissed as cranks who are bitter at being laid off.
Cloud computing is all about visionary modular concepts creating adaptive logistical projection
using a distributed scalable core for multi-tiered background ability resulting in a inverse didactic pricing structure.
I hope I cleared that up. It's actually good to see a healthy level of skepticism on this board.
putting the 'B' in LGBTQ+
Maybe in the IT world but in the electronics world (at least in the UK) its still taught as micros. 6502 assembly is used quite extensively in teaching still here. Civilian industry may like Java and so on but those of us working in systems that require proven reliablity and standards conformity still need to know it.
A thistle is a fat salad for an ass's mouth...
I don't remember "grid computing" being quite the on-demand system that, say, Amazon EC2 is. What makes it cool is the ability to scale it up and down on demand, rather than in months or years.
Or maybe it's some combination of grid computing with virtualization.
And yes, it's pretty much a buzzword. Just like Web 2.0 or AJAX or all the rest. It's a useful abstraction, but not a world-changing "paradigm shift".
Don't thank God, thank a doctor!
No, sadly this one is EASY...
Cloud computing is how computing worked in the 1960-80's - large centralized systems that did everything, and you connected to with dumb terminals. Well it's back, but this time with a different name.
Simple yes, but simple is not exciting.
- Adam L. Beberg - The Cosm Project - http://www.mithral.com/
will place an ad on Dice.com requiring 5 years in depth experience in all aspects of Cloud Computing.
When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
Defining things has always been a problem:
The king's three scholars had accused Nazrudin of heresy, and so he was brought into the king's court for trial.
In his defense, Nazrudin asked the scholars, "Oh wise men, what is bread?"
The first scholar said, "Bread is sustenance; a food."
The second scholar said, "Bread is a combination of flour and water exposed to the heat of a fire."
The third scholar said, "Bread is a gift from God."
Nazrudin spoke to the king, "Your Majesty, how can you trust these men? Is it not strange they cannot agree on the nature of something they eat every day, yet are unanimous that I am a heretic?"
(From The Trial of Nasrudin
A.
lot's of pc's and stuff -|LAN Cloud|->|router |<-->| Internet (big fluffy[scary?] cloud)|<-->|router |<--| LAN 2 Cloud |- lots of other pc's and stuff
(imagine some crappy ascii depiction of the above)
Now we throw a VPN link into this and this becomes the WAN cloud.
Or let's say we get a bunch of leased lines to remote sites and expand our token ring segment off our main LAN...
Of course I didn't RTFA... why would I do that? You really are new here aren't you? Don't let my UID fool you.
Leslie Lamport famously defined a distributed system as "one in which the failure of a computer you didn't even know existed can render your own computer unusable".
http://research.microsoft.com/users/lamport/pubs/distributed-system.txt
In this vein, I would define cloud computing as "a computing system in which the failure of a network you didn't even know existed can render your own computer unusable".
I am sure that there are many other solipsists out there.