Is a ‘Commoditized Cloud’ really for everyone? For most, sooner or later it will be. Is it for every application? Of course not.
The recent Cloud Connect conference in Santa Clara served to sharpen the contrast between traditional IT and the cloud and should be taken as a wakeup call for enterprise IT organizations. To me, the key messages that came through loud and clear in several of the keynotes and many of the breakout sessions essentially focused on:
-
The emergence of the commodity cloud as the most economically viable approach to realizing cloud services
-
The close linkage between the DevOps philosophy (or mindset) to automated systems lifecycle management and the cloud
-
The cloud as primarily a development platform for new applications (as opposed to a migration target for existing apps)
-
Cloud is following the historic route of adoption largely outside of (or despite) IT management and control
Whether you agree or disagree with these ideas, there definitely seems to be a coalescing of the cloud into distinct camps, with the two most prominent being the “commodity-crowd” versus what I’ll call the “traditional enterprise vendor” camp.
Some view this cloud partitioning as between vendor cloud ecosystems, specifically between companies aligned with the OpenStack initiative and those aligned with VMware’s vCloud. The implication – which doesn’t quite hold up – is between “open” and “proprietary”.
For example, Amazon developed their cloud environment with their own proprietary APIs, largely because nothing else existed at the time. So they aren’t especially open, but they are representative of the commodity cloud. There are also companies like Citrix and Cisco that would certainly be viewed as traditional enterprise IT vendors, but they also happen to be serious players in the commodity cloud. Cisco is, of course, the “C” in the VCE (VMware, Cisco, EMC) alliance, but they are also a member of OpenStack and are helping to advance open networking initiatives like OpenFlow. Likewise, the VMware-sponsored Cloud Foundry (http://cloudfoundry.org) is an open-source environment that has been well-received as a non-proprietary development platform.
Regarding the economic viability of one approach over another, it’s important to understand the reasons for considering a cloud approach, the specific benefits that the organization hopes to attain, and what type of legacy applications are in place. Some benefits, like improved utilization through shared resources, can be gained regardless of what kind of infrastructure and virtualization platform a company is on. By developing standard offerings and being able to provision them in an automated fashion, an organization can derive significant benefit to users and improve IT efficiency regardless of the platform. Architectures that provide flexibility can be crafted in a variety of ways and the efficiency of each approach is dependent on the capabilities and limitations of the given organization – the real key is intelligently leveraging your strengths and getting help for your weaknesses.
However, when considering scalability, I think it is no surprise that the “poster children” of the cloud – very large scale environments such as Amazon, Google, Netflix and others with massive server and storage requirements, developed commodity-based solutions to address their unique needs. At such a level, the commodity cloud becomes a competitive requirement. At Cloud Connect, Zynga described the growth of Farmville at launch as going from 0 to 10 million active users in 6 weeks! This would have been nearly impossible in a traditional, non-cloud environment.
Clearly not all organizations are that dynamic. If you have a small number of servers, hardware may not be the most significant cost driver or challenge. Skill limitations may be the major pain point. Even in larger organizations with the leverage to negotiate healthy vendor discounts, hardware may not be the driving cost factor. Things like data center capacity limits, a preponderance of legacy applications, lack of flexibility and slow responsiveness may be the overriding concerns. Implementing the appropriate cloud model in each case can help to address these issues, but the type of cloud will be quite different. The former is likely to gravitate toward SaaS offerings that represent complete packaged solutions while the latter, depending on internal skills and purchasing practices, may seek out the solutions from organizations that can provide the vendor support that they depend upon.
One major promise of the cloud is as an open development platform that can exist anywhere – internal or external, public or private – and is essentially indifferent to the type of platform it runs on. That is great for new applications being built from scratch.
To a large extent, the cloud direction for an organization will depend on its application strategy, the extent to which valuable legacy applications need to be supported, and the requirements of those applications.
The commoditized cloud is a tremendous facilitator for the development of new applications, particularly those designed for massive scalability, and those that can provide resiliency within the application architecture. However, applications that depend on highly available infrastructure do not necessarily benefit from the commodity cloud.
While we are now hearing advocates of both camps expounding on the virtues of each, the reality is that no one approach is right for every environment or application, and we’ll continue to see lots of cloud types and variations for the foreseeable future.
- James Damoulakis is CTO of GlassHouse Technologies