Cloud Stuff- The new buzzword
For as long as I have been in the ICT industry, there always seems to be a technology buzzword that dominates the dialog but no one really agrees on the actual definition of the term, the details behind it or the way to measure the market.
In some cases these issues become resolved and the technology becomes mainstream and understandable. An example of this is the term “switch” when used to describe a network device that passes packets over multiple ports. If you remember when the term showed up over a decade ago, some companies praised the value of switching as a cut-through device versus a store and forward device (meaning the packets spent less time inside the devices buffers and ultimately had lower latency). The issue was that then every multi-port bridge as defined by IEEE 802.1 standards was renamed a “switch”. Soon anything with more than one port on it was a “switch” including things formerly known as routers, bridges, gateways,… Over time the technical purists gave up and the industry just started calling multi-port bridges, routers and other devices layer 2, 3,or 4-7 switches. All that posturing and debate resulted in nothing more than a new name that honestly didn’t matter at all.
In other situations it just fades away as the next big buzzword appears and distracts the industry from the prior dialog. A good but forgotten example of this was the short lived infatuation of Asynchronous Transfer Mode (ATM) technology and other deterministic LAN technologies. The hype was around the idea that if we could make networks predictable, voice, video, and data could all work in a converged way over the same network. Obviously if you look at the fact that today, these types of traffic do work over the same network but not because we achieved deterministic networking but rather because we threw huge amounts of bandwidth at low cost at the problem and then layered on top a “good enough” class of service model. The hype of perfectly engineered networking was lost by the availability of cheap, pervasive capacity with some band aid type control mechanisms.
So here we are with another new buzzword generating a huge amount of hype… cloud computing. Also with cloud computing is a host of new acronyms describing “everything as a service”, XaaS, IaaS, DaaS, SaaS, PaaS…. These are buzzwords because we don’t have a clear definition of them. On sites like Wikipedia, there is a pretty detailed summary of all the possible elements and models that could be considered cloud computing, for example, but all one has to do is read the literature from a few players in this area to see that the language and architecture of this space is far from uniform. For a pretty good dialog on this set of new “thing” and how vague they are, the register.co.uk hosted a pretty long webcast. Its done pretty well but the ambiguity this space has is obvious from the dialog. The question though is if cloud computing is in fact a sustainable and real paradigm shift or just simply a better marketing term for a set of different approaches to IT and compute architectures.
In terms of new and unique properties, I find that the basic elements are not new. Most definitions of cloud computing boil down to using :
- A distributed computing environment – meaning many CPUs are used as a system with a network as the interconnect. The issue is that sometimes this is a classic grid computing model and in other cases it is a much more ad hock collection of interconnected computing resources.
- A level of virtualization – meaning that the processes have little knowledge of the actual compute hardware they run on. Technology such as VMWare is often used for this but by no means is there a uniform architecture for virtualization yet and the degree of virtualization varies widely from one definition and system to the next
- A set of services that can be accessed by software running in the cloud – meaning that many of the functions that one would normally have to implement in a discrete system are offered as “services” to any code running in the cloud. For example real time communications and conferencing could be offered to apps in a cloud as a function. Other traditional discrete services such as identity management or even complex functions such as location functions and tracking of client devices could make up some of that broad services suite. The issue here is that what services a cloud delivers is left to the particular specific cloud so an application implemented in cloud A might not have access to the same “services” on cloud B.
- A web services or other IT friendly programming interface - meaning that instead of low level compute centric interfaces, functions in this type of system are presented as programming interfaces that are native to the IT applications using the cloud. For example instead of making multiple low level calls to invoke a conference call, a programmer in this type of environment would simply execute a basic function such as “invokecall(phone number)” and the call would happen. All the complexity buried in the cloud on the system that specialized in real time communication.
The problem is that in all 4 of these elements, they may or may not be implemented in a system called a cloud.They may also be implemented in radically different ways and at different levels of sophistication. And in many cases they may not even be present. Yet in all of these permutations the system is called a “cloud computing” system or solution. Sounds like hype and buzzwords to me.
Does this mean cloud computing is hype and irrelevant? Not at all, the idea of pulling a distributed network based compute infrastructure together with good vitalization, embedded services and an IT friendly interface to applications is in fact pretty new. It is also very useful. I have spoken to dozens of small companies in the last six months that are able to achieve more rapid development of solutions and greater functionality because they can host their solutions fully or partially in one of many cloud computing systems out there. They also are able to focus on their core value as the cloud computing systems provide them a set of embedded services that if they had to create and implement internally would be far to costly and complex. All of that means that this idea of cloud based computing is of value, the issue is if it is a singular thing or simply a progression of a number of IT systems that happen to provide good synergy today. I am not sure that cloud based computing as a “new thing” is sustainable or even relevant but the sub elements and the ability to use them together are a good step in the right direction. What inevitably will happen is that more of the elements of the IT ecosystem will evolve and become available to a larger base of customers and additional improvements on other portions of the total IT framework will emerge to provide incremental value beyond the four elements mentioned in cloud computing today. Will that continue to be known as cloud computing or will it simply become part of the way we do IT in the 21st century. I am betting on the latter and with that betting that the term and hype over cloud computing will simply disappear under the broad evolution of all parts of the ICT ecosystem. In any event it will be interesting to see the evolution and how disruptive it is to our industry.
If you want to read a recent article on the pros and cons of cloud computing, Forbes.com just published a decent article that I think sums up many of the issues often overlooked and the reality of this hype not being something new.


