API versioning is something a lot of API designers don't worry about until the second version of their API. API versioning, however, is a controversial subject with strong opinions on both version representation and behavior.
Recently by George Reese
The argument for EC2 as a defacto standard is, at some level, the same as it is for any defacto standard: through the EC2 API, you eliminate the need for others to learn some custom API and you can leverage the existing, sizable ecosystem. But there is no such thing as the EC2 API. EC2 is actually many different APIs and adopting the EC2 API as a standard ultimately implies supporting all of those APIs.
I've never seen a perfect REST API. But I have seen some of the most horrible mistakes repeated over and over again by people building heavily consumed APIs. Here's a list of the Good, the Bad, and the Ugly of REST API design.
So many cloud pundits are piling on to the misfortunes of Amazon Web Services this week as a response to the massive failures in the AWS Virginia region. If you think this week exposed weakness in the cloud, you don't get it: it was the cloud's shining moment, exposing the strength of cloud computing.
In my discussion of the Whole Cloud, I assumed as fact that a mature cloud computing infrastructure leverages all kinds of clouds. Given the amount of energy put into arguments on the subject, it's obviously not a given to most people. Today, I want to talk about how these different "pieces of cloud" can be integrated together from a decision-making perspective
A few companies are currently well positioned to create a view of cloud computing that encompasses all aspects of cloud from IaaS to SaaS, public cloud and private cloud, internal and external. A mature cloud infrastructure, however, will be made up of all pieces of the cloud puzzle.
The cloud ecosystem needs a mechanism besides polling that enables monitoring, management, and automation tools to learn about changes in the state of cloud resources. This proposal attempts to define a simple protocol for notifying those tools through a push notifications system rather than polling.
Based on the work I have been doing in cloud computing Europe, Asia/Pacific, and North America, people have been regularly asking me the questions, "How are attitudes towards cloud computing different in Europe?" and "How has cloud adoption differed in Europe from it's adoption in the United States?" In the spirit of attempting to provide some useful insight, I have decided to attempt to write a blog entry and answer those questions as 2010 comes to an end.
In spite of all the innovation that's happened in the recent years in the cloud, cloud networking remains in the dark ages. I expect that 2011 will prove to be the year of the network in the cloud.
The perennial debate on private cloud vs. public cloud continues to flare up anywhere cloud computing is being discussed. One of the most often repeated myths favoring private cloud deployments is that they are "more secure" than public clouds. It's complete nonsense.
