13 October 2009
Cloud or Not?
As it seems people still just don't get what is, and what is not (*cough*Sidekick*cough*) cloud computing, I've put together a (tongue-in-cheek) flowchart to help you decide:
Subscribe to:
Post Comments (Atom)
7 comments:
Hi Sam,
not sure about some aspects in the flowhcart. It seems that the definition chages depending on who will use it, which doesn't sound perticularly useful does it? For instance, if there is an IT department delivering cloud services to other departments within the same company, using your flowchart employees will end up arguing about whether they actually have a cloud or not :-)
Also, what if the same department makes use of its own cloud services for their own purposes (e.g. for testing)? Is it not a cloud anymore?
I think the point is on whether you know the exact servers where your app will run and not where the DC or cloud is located; whether the provision will scale automatically on demand or not; whether you have to worry about maintenance or not.
cheers
Sorry, did I not mention that it was tongue-in-cheek?
:P
Yeah true, but I still thought you were trying to convey some basic principles -albeit with the irony sensor turned on. But, if it was totally ironic (and meaningless) then I happily retract my previous comment :-)
The middle outcome; I can't believe it's not cloud, makes it too confusing for foreigners (two negatives). Feels like a trick somehow.
Again, it's a joke. I use "I can't believe it's not cloud" as you would "I can't believe it's not butter"... it might look and taste like butter, but we all know it isn't. Similarly an internal VMware installation may look and feel like EC2, but we all know it isn't - there are advantages and [lots of] disadvantages.
I like it (and I got the "joke")
It helped me solve a dilemma (g) -- see my post at cloudynews.com on the Nook
Loved the schematic, have no problems understanding the conveyed meaning. ;)
Post a Comment