Since Citrix gave Cloudstack to the Apache Software Foundation, there has been a lot of blogging, tweeting, and arguing about whether cloud computing software vendors should simply let Amazon AWS drive cloud computing standards. My answer is no. First, I don't think Amazon even wants to be the standard and second, standards should be developed independently of any single vendor. It's time for the stakeholders--enterprises, vendors, open source projects, and anyone else interested to start scoping, developing, and implementing standards that everyone can use. If that doens't happen, the cloud landscape will continue to be fragmented to everyone's detriment.
With Amazon getting Cozy with Eucalyptus, many people, including Informationweek's Charlie Babcock, are wondering if Amazon will try to stop others from mimicking it's API in similar manner that Oracle is suing Google over the latter's use of the Java language semantics in Android. There doesn't seem to be any prohibition to mimicking Amazons API in their license agreements, but that didn't stop Citrix from pointing out that one of the benefits of using their commercial offering of Cloudstack (which is tightly integrated with AWS), is indemnification of its use in the case of legal action, presumably from Amazon.
The big question being debated, without Amazon taking a position what so ever, is what the company should do with their API. Dan Woods writes in Forbes that there are three Questions Amazon Should Answer About Its Cloud Strategy 1) Are there limits to the use of Amazon's APIs? 2) How will community experience inform the evolution of Amazon's APIs? And 3) What is the process that will govern the evolution of the Amazon APIs?
To Continue Reading: Click Here
------------------------------------------------------
Source: networkcomputing.com
By: Mike Fratto
No comments:
Post a Comment