You could take a very purist approach and say Theres no such thing as an internal cloud, because by definition its use of external resources to a large extent, Smith says.
However, theres a bit of method to the madness, in clouds double meaning. Its a question of perspective: for users, the cloud can be seen as an internal resource they tap into it through their PCs without regard to its location. But for producers, those who build and maintain it, cloud is typically thought of in its classic definition as external.
Despite this reasonable explanation from Smith, he says You see a lot of people talking past each other on this.
Particularly obfuscating is the use of cloud to refer to virtualization. Because cloud has often been used as a synonym for Software as a Service. And now that cloud is also used to mean virtualization, that suggests that virtualization and SaaS are the same thing which is clearly not true.
I dont use it as a synonym for virtualization, Smith says, and when I hear people do it, I immediately understand their perspective and will talk with them at that level. Its kind of hopeless to say its not cloud computing, because you can see the reasoning behind how they got to where they are its just not worth fighting about.
The problem, ultimately, is that the term cloud is still new, yet has already grown to encompass a dizzying array of configurations.
At this rate, where are we headed?
In the future, a conference call will be referred to as 'cloud conversation' because its voices moving freely over a network, accessed and inputted from both internal and external nodes (also known as phones, soon to be called cloud-voice-input modules). The article youre reading might be called cloud journalism because it can flow anywhere over the Internet, or can be sent internally over an intranet.
In fact, now that cloud computing is so all-embracing, the only thing that can no longer be called a cloud is, well, an actual cloud. Like, the kind that sits up in the sky, made of water.
Because these fluffy white things cannot move freely through disparate interconnected environments. They can only exist in one very narrow layer of the atmosphere, say 6,000 to 20,000 feet, in very specific atmospheric conditions. They cant move like an app on a virtualized server network. They cant come to earth, they cant go out into space. Actual clouds are far too limited to deserve the term cloud. For clarity, we should start calling them limited-mobility water retention events.
Oh dear, we cant go for a walk today, because the sky is filled with limited-mobility water retention events. And we might experience Water-as-a-Service (rain). So we better bring our plastic-based mobile cloud firewall (umbrella).
Alas, if were not careful, the entire rickety structure of IT jargon might collapse. But actually, based on the history of cloud computing, maybe it already has.