Home > Cloud Computing, Software Development, vSphere API > Why DoubleCloud? The mission statement in short

Why DoubleCloud? The mission statement in short

January 21st, 2010 Leave a comment Go to comments

After setting up this blog site, I updated my LinkedIn profile. This morning, my colleague Gilbert left me a comment saying “why not hybrid cloud?” I know he was kidding, but it’s a good time to explain why I got this name.

The basic idea behind the name is the following equation:

Time to learn how to "Google" and manage your VMware and clouds in a fast and secure


DoubleCloud = PublicCloud + PrivateCloud

or as some people prefer

DoubleCloud = ExternalCloud + InternalCloud

Although with slightly different terms, they convey pretty much the same message.

Now you know the name DoubleCloud is actually the shortest version of the mission statement of this blog site — it will cover both internal cloud and external cloud, which can be used separately, or together (then you can call it hybrid cloud).

Because virtualization is an enabling technology for cloud computing, VMware has a unique postion and influence in the cloud market given its leadership in virtualization market with vSphere and other products.

As many of you already know, vSphere has provided a solid platform for internal cloud, and comprehensive management APIs. These APIs are known as “under the hook” APIs, much more than a cloud user needs. Most of our vSphere Java API users know what “under the hook” means.

To meet the needs of the cloud users, we need much simpler APIs that just fit their needs: no more, no less. This API is the vCloud API, a “driver seat” API for the cloud users. The cloud users here are not the end users, but developers or admins who need to manage their cloud entities like VM or automate their IT processes. I will cover more on the vCloud API in the future.

Of course, we won’t stop at VMware cloud, but will cover other vendors and technologies with full stack from IaaS, PaaS to SaaS.

Stay tuned…

  1. No comments yet.
  1. No trackbacks yet.