Microsoft is officially launching the commercial operations of its cloud offerings in China today. It’s been only nine months since Steve Ballmer, the former CEO of Microsoft, made the announcement in Shanghai that Windows Azure — now renamed Microsoft Azure — would be available for preview in the Chinese market.
I call that Episode I of the China Cloud War. In the report that I published at the time, “PaaS Market Dynamics in China, 2012 To 2017”, I made three predictions — predictions that are now being fulfilled. More global players are joining the war; customers have gotten familiar with cloud concepts and are planning hybrid cloud implementations for their businesses; and traditional IT service providers have started to transform themselves into cloud service providers.
I talked with Microsoft and Citrix last week, and I strongly believe that Episode I has ended and Episode II has just begun. In the battle for partner ecosystems and real customer business, here are the three major plots that enterprise architects and CIOs in China should watch unfold:
The thrree kingdoms will fight with the gloves off. In my blog post last year, I described three kingdoms of global vendors in Chinese cloud market: Microsoft, Amazon, and vendors behind open source technology like OpenStack and CloudStack.
Microsoft is leading the market as the first company in China to provide unified solutions for public cloud, private cloud, and hybrid cloud across infrastructure (IaaS) and middleware (PaaS). This builds on its deep understanding of enterprise requirements, its massive developer base, and the ease of use on the Windows platform.
Usually when a product or service shouts about its low pricing, that’s a bad thing but in Google’s case there’s unique value in its Sustained-use Discounts program which just might make it worth your consideration.
I know, more control is an axiom! But the above statement is more often true. When we're talking about configuration control in the public cloud it can be especially true, as control over the configuration of your application can put control in the hands of someone who knows less about the given platform and thus is more likely to get the configuration wrong. Have I fired you up yet? Then you're going to love (or loathe) my latest report, published today.
Let's look at the facts. Your base configuration of an application deployed to the cloud is likely a single VM in a single availability zone without load balancing, redundancy, DR, or a performance guarantee. That's why you demand configuration control so you can address these shortcomings. But how well do you know the cloud platform you are using? Is it better to use their autoscaling service (if they have one) or to bring your own virtual load balancers? How many instances of your VM, in which zones, is best for availability? Would it be better to configure your own database cluster or use their database as a service solution? One answer probably isn't correct — mirroring the configuration of the application as deployed in your corporate virtualization environment. Starting to see my point?
Fact is, more configuration control may just be a bad thing.