Public. Private. Hybrid. Cloudburst. Much of the discussion about cloud computing focuses on deployment options and choices, with a surprisingly large number of enterprises inclining toward internal private clouds-that is, a cloud-capable infrastructure residing within a company's own data center.
The talk of CloudWorld this week was VMware's acquisition of SpringSource. The top-of-mind chatter focused on the price: US$400 million plus, a very large sum for a company doing perhaps US$25 million in revenues. Certainly there was a good bit of envy in this type of conversation. And, of course, the fact that SpringSource is an open source company further makes the number even more eye-watering.
A couple of weeks ago Forrester released a report on cloud computing, based upon a survey of small and large enterprises located in North America and Europe. I was particularly interested in its findings as it addressed the question of private (internal) cloud computing.
Private clouds are a hot topic these days, but not everyone agrees on a definition or the potential benefits.
The topic of private clouds is heating up. A private cloud is, essentially, a cloud computing capability dedicated to one organization. The term "internal cloud" is often used for this kind of functionality, but as many people point out, the term "internal cloud" conflates functionality with location. T
Nick Carr was right and I was wrong. Sort of, anyway.<br/>