Every once in a while, the machinery of marketing goes haywire and starts labeling all manner of things with inappropriate terminology. The general rationale of most marketers is that if there’s a band wagon rolling along somewhere and gaining some traction in the marketplace, it’s best to jump on it while it’s rolling. After all, much of the challenge of marketing products is getting the attention of your target customer in order to get an opportunity to pitch products or services to them. Of course, if it doesn’t work with one band wagon, as the old adage goes, try, try again. This is why we often see the same products marketed with different labels and categories applied to them. Sure, the vendors will insist that they have indeed developed some new add-on or tweaked a user interface to include the new concept front and center, but at the very core of it, the products remain fundamentally unchanged.
Now, I don’t want to sound overly pessimistic about product marketing and the state of IT research & development, since the industry couldn’t exist without innovations that are truly new and disruptive and change the very face of the market. However, this sort of innovation often comes not from the established vendors in the market (who have customer bases to grow and defend), but rather from small upstarts that have nothing to lose. It is in this context that we need to evaluate some of the marketing terminology currently coming to the fore around the Cloud Computing concept.
ZapThink has had many positive things to say about Cloud Computing, and we do believe that as a business model, technological approach, and Service-oriented domain it will have significant impact on the way companies large and small procure, develop, deploy, and scale their applications. Indeed, we’re starting to see hundreds of companies that develop whole products and services without procuring a penny of internal IT hardware or software resources. This is the bonanza that is Cloud Computing.
Yet, we’re now starting to see the emergence of a more perplexing concept called “Private Clouds”. If the benefit of the cloud is primarily loosely-coupled, location-independent virtualized Services (implemented in a Service-oriented manner, of course), and we’re doing this with the intent of reducing IT expenditures, then is there any value in a new concept called “Private Clouds? How does the addition of this word “Private” add any value to the sort of Service-oriented Cloud Computing that we’ve been now talking about for a handful of years? Is this a valuable term, or mere marketing spin?
To attempt to gain some clarity around this issue, ZapThink reached out to a number of pundits and opinion-leaders in the space to get their thoughts and definitions on Private Cloud, and to no surprise, the definitions all varied significantly. Let’s explore these definitions and see what additional value (if any) they contribute to the Cloud Computing discussion.
Private Cloud Concept #1: Company-Owned and Operated, Location-independent, Virtualized (Homogeneous) Service Infrastructure
My colleague, Jason Bloomberg, is of the opinion that a Private Cloud consists of infrastructure owned by a company to deploy Services in a virtualized, location-independent manner. What differentiates Private Clouds from simply implementing clustered applications or servers, is that the Cloud is not built for a specific Service or application in mind. Rather, it is an abstracted, virtualized environment that allows for deployment of a wide range of disparate Services. It is important to note that in practical terms, companies will most likely not implement this vision of Private Clouds using a diversity of heterogeneous infrastructure. Indeed, it is in their best interests to control costs and complexity of support, training, and administration by implementing their Private Clouds using a single vendor stack. So, this vision of Private Clouds is often a single-vendor (homogeneous) cluster of virtualized infrastructure that enables location-independent Service consumption. Of course, implementing any sort of homogeneous stack reduces the need for loosely-coupled Services, and thus weakens the Service-Oriented Cloud Computing value proposition as a whole for that company.
Private Cloud Concept #2: Virtualization Plus Dynamic Provisioning (Elasticity)
In a response to a Facebook post, Jean-Jacques Dubray comments that the above definition doesn’t go far enough. Rather, in order for the company-owned and implemented infrastructure to be considered a Private Cloud, it must include the concept of “elasticity”. Specifically, this means that the hardware and software resources must be provisioned in a dynamic manner, scaling up and down to meet changes in demand, thus enabling a more responsive and cost-sensitive approach to IT provisioning. This idea of Private Clouds sounds a lot like the Utility Computing concept sold as part of IBM’s decade-old vision of On Demand Computing. From this perspective, a Private Cloud is company-owned On Demand Utility Computing implemented with Services instead of tightly coupled applications.
Private Cloud Concept #3: Governed, Virtualized, Location-Independent Services
In a response my Tweet on the subject, David Chappell comments that the Private Cloud is really a response to some of the security and governance issues raised by the (public) Cloud. Specifically, he states that a “private cloud (equals) more control over what and how”. Reading between the 140 character lines, I can guess that his perspective is that a private cloud is a governed cloud that enables virtualized, governed, location-independent Services. For sure, there has been a lot of consternation over the fact that the most popular “public” Clouds share infrastructure between customers and require that data and communications cross the company firewall. This stresses out a lot of IT administrators and managers. So in response, these folks insist that they want all the technological benefits of Cloud Computing, but without the governance risk of having it reside in someone else’s infrastructure. Basically, they want the virtualization, loose coupling, and location-independent benefits of Cloud Computing without the economic benefits of leveraging someone else’s costs and investments. Basically, they would rather own a version of the Amazon EC2 Cloud than use it, solely for reasons of governance.
Many people are indeed concerned about those supposed governance and security draw-backs of Cloud Computing. However, rather than simply dismissing the economic benefits of the public Clouds, why can’t we simply approach Private Clouds as a veneer that we place on top of the public Clouds? Couldn’t companies impose their governance and security requirements on third-party infrastructure, using company-owned governance tools and approaches to manage remote Services? Couldn’t we simply demand that the public Clouds provide greater governance and security control? Basically, does the addition of the term Private provide the same sort of value as it does in the context of the Virtual Private Network (VPN)? We didn’t throw out the Internet because it was insecure and create a Private Internet. So, why should we do the same with Cloud Computing and create Private Clouds?
Private Cloud Concept #4: Internal Business Model for Pay on Demand Consumption of Location-Independent, Virtualized Resources
JP Morgenthal takes an entirely different perspective on the Private Cloud concept and insists that the primary value of any Cloud, whether implemented privately or acquired from a public vendor, is the business model of pay-as-you-go Service consumption. From this perspective, a Private Cloud is an internal business model that enables organizations to consume and procure internal, virtualized, loosely-coupled Services using a pay on demand model similar to a chargeback mechanism. Rather than an IT organization paying for and supporting the costs of the business users in an aggregate fashion, they can provide those resources using the same business models employed by Amazon, Google, Salesforce.com and others in their public Clouds. In order to realize this vision of Private Clouds, companies need a means to enable transactional Service purchases, auditing of Service usage, and organizational methods for enabling such inter-departmental charges. At the most fundamental level, this vision of the Private Cloud treats IT as a business and a Service provider to the rest of the organization.
Private Cloud Concept #5: Marketing Hype, Pure and Simple
TechTarget offers the most cynical view of the Private Cloud. In their words, a Private Cloud is a “marketing term for a proprietary computing architecture that provides hosted services to a limited number of people behind a firewall.
Marketing media that uses the words “private cloud” is designed to appeal to an organization that needs or wants more control over their data than they can get by using a third-party hosted service…” Basically, they opine that the term has marketing value only. Where does this place IT practitioners? Reading between the lines, they encourage us to ignore the usage of the term.
More Fodder for Pundits
Thomas Bittman from Gartner recently posted a rather snarky blog post that says that if we don’t get Private Clouds, we’re basically silly people who are missing the boat. In that article, he states, “Can you find a better term? Go ahead.” Yes we can. Service-oriented Cloud Computing adequately defines an architectural and infrastructural approach to develop location-independent, loosely coupled Services, in a manner that virtualizes and abstracts the implementation of these Services. What additional value does the term “Private” add to that? It’s not entirely clear, and as we can see from the discussion above, there’s no consensus.
Adding more fuel to the fire, a well-publicized video of Oracle’s Larry Ellison and follow-up audio post is now making the rounds where he (humorously or embarrassingly, depending on your perspective) pokes holes in the Cloud Computing concept as a whole and chastises IT marketing efforts. Regardless of where you stand on the Cloud Computing discussion, the video sheds some light on Oracle’s perspective on this whole mess. While it would be hard to say if Ellison speaks for all of Oracle (although you would think so), it indicates that even vendors are starting to strain at the marketing hype that threatens to devalue billions of dollars of their own product investment over the prior decades.
The ZapThink Take
The fact that there’s no single perspective on Private Cloud might indicate that none of the definitions really warrant separating the Private Cloud concept from that of Cloud Computing as a whole — especially the Service-Oriented sort of Clouds that ZapThink espouses. One reasonable perspective is that the definitions discussed above are simply differing infrastructural and organizational approaches to implementing Service-oriented Cloud Computing. However, those approaches should not warrant a whole new term and certainly not millions more in infrastructure expenditure. Trying to create a new concept of Private Clouds from any of a number of perspectives: architectural, infrastructural, organizational, governance, business model, seems to introduce more confusion than clarification. After all, shouldn’t all clouds, Private or not, have many of the benefits described above? Doesn’t the concept of a private, company-owned Cloud in some ways weaken the Cloud value proposition? Who really benefits from this Private Cloud discussion — IT practitioners or vendors with products to sell?
The point of any new term should be to clarify and differentiate. If the term does neither, than it is part of the problem, not the solution. However, when vendors start pitching their warmed-over middleware stacks and now-dull Enterprise Service Buses (ESB) as “Private Cloud” infrastructure stacks — ask yourself: does this change what you are doing now, or is this the beating of the band wagon’s marketing drum? The goal is not to buy more stuff — the goal is to provide the business increasing value from their existing IT investments. This is the purpose and goal of enterprise architecture and the reason why IT exists in the first place.