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.
At this time 12 months ago, we released our predictions for what changes in the market would be brought about by the maturing of cloud computing. Looking back on the year, we can now see that, while the promise of a maturing market was strong, maturity was by no means uniform and thus our predictions proved to be a mixed bag.
1. We’ll finally stop saying that everything is going cloud. Grade: A. While the C-suite might still be preaching this as a long-term vision, we got real about what should and should not go to the cloud given its current maturity and capabilities. The guiding principles of architecture and economic model served as sufficient evidence that many traditional workloads have no business on the public cloud. And we started to see early signs of enterprises recognizing that the private cloud isn’t the new name for virtualization but is indeed a separate environment and not all apps in the data center are destined for this pool.
After a couple less-than-home-runs in the cloud game, it looks like CenturyLink might just have a real contender. The US midwestern telecommunications leader pulled the trigger on yet another acquisition this morning - Tier 3, a legitimate cloud platform provider. The real question is whether this is the latest in a long string of acquisitions that have failed to hit the mark, or a sign that they finally got it right.
CenturyLink is a Lego company built through a string of acquisitions all bolted together. It rolled up several telecom players to get to its current size and presence in that market. And it has bought now three cloud companies.
Every client (especially every government client) who says I’ll never use cloud services with highly secure data needs to hear this story. In no more sensitive a place than law enforcement is just such a value proposition playing out.
Police departments in 18 states in the US, and soon Canada, are dramatically increasing the efficiency of commercial use of highways through a disruptive SaaS solution that costs a fraction of the incumbent service and mixes well with their permitting and inspection databases.
If you drive toll roads or bridges you know the value of Drivewyze. In rush hour, you can wait 10-25 minutes to pay your toll with cash or you can sign up for an electronic toll system that lets you breeze past. Drivewyze does the same for commercial trucks and fleets but not at toll booths but weigh stations, that take much longer to get through. And in the trucking business every minute lost at a weigh station can cost thousands of dollars in lost delivery time. For law enforcement the value is even higher as any time lost inspecting a safe truck is time not spent stopping an unsafe one.
The system works by helping known-good drivers and trucks register with the weigh station wirelessly as they approach it on the highway, get an all-clear, then drive right by. Trucks send their credentials to the weigh stations using any mobile device they happen to have – iPhone, Android, Blackberry. Anything with a cellular connection will do the trick. At the weigh station, they receive the information about the driver over whatever equipment they have – aging PCs and laptops are most common. The system checks each driver and truck against long-standing databases of safety records, expired licenses, past weigh station checks and other information that would indicate an unsafe driving circumstance.
So far the latter seems to be the prevailing trend as the majority of public cloud platforms and private cloud software solutions start with the foundation of server virtualization. The bare metal options are being positioned more for two purposes:
Auto-provisioning new nodes ofthe cloud - bare metal installation of the cloud solution and the hypervisor
New compute resource types inthe cloud - using new automation capabilities to add a complete physical server to a customer’s cloud tenancy, as if it were just another virtual machine.
Adobe Systems is a pioneer and fast mover in the public cloud and in so doing is showing that there is nothing for infrastructure & operations professionals (IT Ops) to fear about this move. Instead, as they put it, the cloud gives their systems administrators (sysadmins) super powers ala RoboCop.
This insight was provided by Fergus Hammond, a senior manager in Adobe Cloud Services, in an analyst webinar conducted by Amazon Web Services (AWS) last month. Hammond (no relation to Forrester VP and principal analyst Jeffrey Hammond) said that Adobe was live on AWS in October 2011, just 8 months after its formal internal decision to use the public cloud platform for its Adobe Creative Cloud. Prior to this there were pockets of AWS experience across various product teams but no coordinated, formal effort as large or strategic as this.
Q: Is this a private cloud? AWS said it doesn't believe in private clouds.
A: Yes, despite AWS' protests to the contrary, this is a private cloud. According to the documents that have thus far been made public from this proposal, the CIA is looking for a cloud service (an Infrastructure as a Service) offered on a dedicated set of resources isolated to a specific customer and deployed on CIA-owned resources from within a government owned and operated facility.
Q: Would this be AWS' first private cloud?
A: Yes and no. Yes, it would be the first implementation of the AWS services atop a customer-owned infrastructure and facility asset base. But no, it would not be the first time AWS has delivered an isolated environment offering its services. AWS's GovCloud is also a private cloud for the greater US Government. FedCloud is operated from an AWS-owned facility on AWS owned assets.
Q: Is this a community cloud? What's the difference between that and a private cloud?