Happy April Fools! The Google Cloud API: cloud coverage anywhere, anytime
April 1st, 2012 | Published in Uncategorized, Google App Engine
We are thrilled to announce a project the App Engine team has been working on for a long time: the Cloud API. The Cloud API allows developers unprecedented control over cloud deployments in their area.
We think the Cloud API is a huge step forward for developers. For the first time, developers can simply and easily gain cloud coverage in locations around the globe within minutes. With the Cloud API developers can drive increased cloud awareness for a wide range of new users and enterprises. This will not only allow totally new applications in the agricultural and metrology sectors to flourish but also provide a welcome addition to mobile, social and gaming. The Cloud API provides the scalability you would expect from App Engine with clouds seeded on demand and dispersed when they are no longer needed. Clouds are created using cloud engines which are specially designed jet engines with three fins.
A Cloud Deployed Using the Cloud API. Imagery ©2012 GeoEye, DigitalGlobe, Cnes/Spot Image, TerraMetrics
The Cloud API is supported in Python, Java and Go, check out the Getting Started Guide to find out how simple it is to integrate clouds into your applications.
As with other parts of App Engine, the Cloud API is backed by an SLA of 99.95% uptime along with an accuracy of ±5m. Clouds come in configurable sizes ranging up to 5m3 for free customers with paid and premier customers able to extend clouds to 10km3.
Pricing for the Cloud API are based on the likelihood of cloud in the location the cloud is requested. A cloud pricing calculator will be released in the coming days, however example pricing is provided below:
Example Location | Likelihood of Cloud | Price/Cloud Hour/10m3 |
Seattle, WA, US | 55% | Free* |
Brisbane, AU | 20% | $0.10 |
Yuma, AZ, US | 10% | $0.20 |
*Removal of cloud from high cloud areas such as Seattle has a cost of $0.10 per Cloud Hour per 10m3.
If you have any questions or comments send them to the App Engine group. We'd love to hear from you.
- Posted by the App Engine team