Two Cloud Myths Busted: Lock-in And Locked Up
Posted 30 April 2012 - 09:05 PM
Nvidia has CUDA, but the rest of the industry (even Nvidia) agree on OpenCL
The same will happen with Cloud API. Amazon and Google will likely continue to develop a propietary API while the competition will create and follow standards. They will commoditize the product, but that is better than being put out of business.
Posted 01 May 2012 - 04:41 AM
I would like to give an example that breaks vendor lock-in. GigaSpaces (for which I work) produces Cloudify - an open source tool for taking any application (any stack), deploying it on any cloud, managing and monitoring it without changing the application code, and still retaining full control and visibility of the entire process. cloudifysource.org shows that it's not magic but a reality.
You are literally free (as in speech) to choose the processes that make up your app and free (as in speech) to deploy them on the cloud of your choice. Oh, and it's for free (as in beer).
Posted 09 May 2012 - 11:58 AM
Dependency is not the same as lock-in. You can be dependent on a technology but if it's standards compliant, free and open source, or otherwise provides mechanisms for appropriately extracting and porting your data then you won't be locked into it.
Where cloud computing can create a worse situation, for example with APIs, is with changes and other potential disruptions in the provider's business. See even if your entirely locked-in to a propriety vendor's APIs, as an on-premise solution at least you have the software and control it. If the vendor goes out of business your software doesn't stop working. If the vendor releases a new version or changes its APIs that doesn't impact the version you have installed.
On the other hand, if a cloud-based vendor goes out of business or decides to change its APIs, there is a very real risk that your usage of it may not work. You do not have much control over that. The lock-in that you experience for a cloud-based system is qualitatively different than an on-premise one and the ramifications of this ought to be taken into consideration.