One of the most interesting announcements of the year was Microsoft's Azure Appliance — a container of 1,000 servers, delivered to your data center, running an up-to-date private version of the Azure Cloud platform. Last year we saw the introductions of Cisco's UCS, the Cisco/VMware/EMC VCE consortium, V-Block system blueprints and Acadia JV, all intended to help their customers achieve utility computing more quickly. Well if that's the goal, isn't something like the Azure Appliance an even better answer? Of course you have to have some respect for the importance of the Windows software and business ecologies, and you have to think Azure is pretty interesting on its own, but with those caveats isn't the appliance version interesting! The initial package (presumably similar to the container level packaging which Microsoft uses to build out Azure and their other large properties) is inappropriate for most but not all (huge chunk of platform, specific cooling and power requirements) but is a natural first step. With the issues of non-Microsoft multi-tenancy and new network topologies understood, a next step of creating smaller packages seems pretty straightforward (Microsoft has already said they are moving to a smaller granularity for their own data centers). What Microsoft clearly understands (or at least Bob Muglia clearly understands) is the difference between having a customer build their own utility solution out of the pieces (Windows Server, Hyper-V, System Center and Virtual Machine Manager, SQL Server, Exchange, SharePoint,...) and giving them an up-to-date and evolving platform is pretty dramatic. UCS and VBlock customers are still dependent on the product development and release cycle of VMware, EMC, Cisco and others, and still fully responsible for the pain and anguish of integrating new versions.
If there's one thing that the banking collapse taught us all was that in the long term, you can't ignore the risk factors in a business. Risk has a nasty habit of landing on your front doorstep when it's least welcome — just ask someone who worked for Lehman. In a similar but different way, cloud computing has collateralized risk in a way which might come back to haunt us. Just a few years ago when a group wanted to create a new product they'd often have to build a data center for development, test and deployment. If it was a start-up, venture capital was used to pay for the data center with the investors essentially holding the risk if something went wrong. With Cloud Computing the risk taker, while still present, has changed. Instead of building their own datacenters, startups now use their credit cards and rent computing power from companies like Amazon. Essentially the server providers who in the past had customers with multi-year managed server contracts (little risk) now have customers with no commitments at all, just monthly MasterCard bills. From a risk perspective, the risk moved from the venture investor (or whoever funded product development) to the service provider. This doesn't sound like too big of a deal unless the service provider inadequately accounts for the risk that they're facing. For instance, what if the service provider didn't adequately account for utilization and server demand surged with unexpected consequences. In the past, this sort of risk was borne by the investors and the company developing the product which could lose its investment if it got things wrong — but it could only hurt itself. In our new world the risk is spread across the entire customer base of a cloud service provider who may not completely understand the impact of a surge and inadvertently bring down a large portion of their customer base and anything else that might be running on their system. The risk that came with bringing new services online is still there; it's just taken a completely different form, might not be fully understood and could come crashing down when you least expect it. — Sound familiar?
In his CA keynote, Dr. Ajei S. Gopal, EVP of the Products and Technology Group, introduced the best simple way of understanding the ongoing transition to "Cloud" computing that I've heard so far. He said that IT is going through a transition very much like what manufacturing has gone through for many companies over the last decade. For example, today Cisco manufactures essentially nothing, instead using a network of contract manufacturers and logistics specialists. Ajei's point was that if you're part (say) of Cisco's Global Supply Chain Management team ("manufacturing") your mission is getting high-quality products quickly to Cisco's customers at the lowest possible cost (where "high-quality" and "quickly" are complex issues). If a company does its own manufacturing there is the risk of focusing on (say) the fact that you are best-of breed at wave soldering 21-layer PC boards, and thinking that's what counts the most, whereas the supply chain mission is pure and aligned with the business. Legacy IT shops are very much like legacy manufacturing. Moving forward, more and more options open up for outsourcing aspects or all of IT (e.g., use of SP resources, SaaS, ...). The new (and better aligned) IT mission is a direct analogy: how can you deliver high-quality, agile services and applications to the business at the lowest possible cost?