As a public cloud service optimized for Big Data applications, GoGrid gives developers access to a number of open source platforms, including Hadoop, Apache HBase, Cassandra, MongoDB, and Riak. Trying to fuel what GoGrid CEO John Keagy describes as an open data services (ODSs) market, GoGrid provides the ability to stand up applications on multiple platforms in a way that helps developers avoid getting locked in to one particular architecture. Now GoGrid is close to taking that concept one step further by exposing an API to the GoGrid cloud platform.
Our API directory now includes 78 hosting APIs. The newest is the MongoHQ API. The most popular, in terms of mashups, is the Heroku API. We list 13 Heroku mashups. Below you’ll find some more stats from the directory, including the entire list of hosting APIs.
Our API directory now includes 97 cloud APIs. The newest is the Yubikey API. The most popular, in terms of mashups, is the Twilio API. We list 335 Twilio mashups. Below you’ll find some more stats from the directory, including the entire list of cloud APIs.
RESTful approaches to APIs have made them easier to deploy and consume, leading to a recent explosion in the number of available APIs. One byproduct of such growth is there are a lot of APIs offering similar or even duplicate services, but that have very different approaches to delivering their APIs. Cloud computing and social networking are two areas where we’ve seen the growth in APIs. As the number of APIs grow, the need for interoperability increases.
When Amazon announced a public beta of its cloud computing infrastructure in 2006, it was the beginning of the new computing era in which you can consume and pay for computing resources per use. Today we have a lot of public clouds, however, when you build and deploy your application you are often bound to a single cloud provider through its proprietary API. DeltaCloud provides you with unified API across major cloud providers that you can use to manage your virtual machines in major clouds such as EC2 or Rackspace.
One of the big debates these days when it comes to cloud computing center around portability and interoperatbilty between providers. That is, if you build an application on Amazon’s EC2 or Google’s AppEngine or Force.com, or store your data on Box.net or Amazon’s S3, how hard is it to port your application or move your data to another cloud provider? If you develop on a given platform, how locked-in, or not, are you? And beyond that, could developers benefit from having standardized APIs to develop to without having to learn a new model and interface each time. As you’d expect, there’s no easy answer to this.