New York-based cloud computing startup 10gen launched today with backing from CEO Kevin Ryan’s startup network, Alleycorp. It makes sense, since with several ventures already under his belt, Ryan probably has enough customers to both justify the buildout and break even right away. And the founders know scaling, having built out ad network DoubleClick.
But is it always a good idea to build your own cloud when you get big enough to do so?
Yesterday, for example, I had a great chat with Lana Holmes, a Bay area startup maven, about product management and how to focus on doing the one thing that matters to your company. “The example I use is Amazon,” she said. “They just focused on selling books. And look at them now.”
At their root, Amazon’s EC2 and S3 offerings are the result of excess capacity from sales. The offerings have paved the way for an online world in which compute power is a commodity. The company has subsequently built, on top of those offerings, a layer of billing, services and support for them.
The motivation behind the creation of 10gen is similar: If you successfully launch a number of web firms, at a certain point the economies of scale of others’ clouds starts fall away and you may as well run your own.
It’s easier than ever to launch your own cloud. You’ve got grid deployment tools from folks like 3Tera and Enomaly. Virtualization management can be had from the likes of Fortisphere, Cirba and ManageIQ, to name just a few. And license management (built into cluster deployment from companies like Elastra) is knocking down some of the final barriers to building a cloud that you can offer to third parties as well.
But imagine a world in which there are hundreds of clouds to choose from. Moving a virtual machine is supposed to be as easy as dragging and dropping, and cloud operators will hate that. They’ll resist, putting in proprietary APIs and function calls. Applications and data won’t be portable. You’ll be locked in to a cloud provider, who will then be free to charge for every service. Sound familiar?
My guess is that as the cloud computing market grows and matures, one (or more) of three things will happen:
- Standardization and portability, in which consortia of cloud vendors agree to a standard set of APIs and coding constraints that guarantee interoperability. This isn’t just about the virtual machines; they’re fairly standard already. It’s about the data storage systems and the control APIs that let cloud users manage their applications. This is the mobile phone model, where number portability is guaranteed and there are well-known services like voice mail and call forwarding.
- Shared grid computing, in which smaller clouds sell their excess capacity to bigger clouds. This would let the big cloud dominate while paying the smaller cloud just enough to stop it from launching an offering of its own. Think of this as the electric company model, selling computing between clouds the way a solar-powered household can pump excess electricity into the power grid.
- Specialization, where clouds are good at certain things. You’ll get OS-specific clouds (Heroku is already providing optimized Rails deployment atop EC2.) It’s only a matter of time before we see clouds tailored for specific industries or the services the offer — anything from media to microtransactions. Sort of like the cable channel model, with specialized programming that allows niche channels too survive.
Whatever happens, it’s clear that good old-fashioned branding, plus a healthy dose of experience, will be key to winning as a cloud provider.
During a panel at Interop last week that I sat on with folks from Amazon, Opsource, Napera, Syntenic and Kaazing, I asked the audience how many of them would entrust Microsoft to run a cloud with Microsoft applications, and how many would prefer to see Amazon running a Microsoft kernel on EC2. Roughly 75 percent said they’d trust Amazon to run Microsoft’s own apps rather than Microsoft.
So when’s the right time to launch a cloud computing offering of your own? Unless you have the branding and reputation to support that launch — or you can re-sell excess capacity to partners or specialize — maybe never.