Google Cloud Storage: Difference between revisions
Content deleted Content added
added infobox and started content edit |
added design |
||
| Line 13: | Line 13: | ||
'''Google Storage''' for Developers is a [[Restful|RESTful]] [[online storage]] [[web service]] for storing and accessing your data on [[Google]]'s infrastructure. The service combines the performance and scalability of Google's cloud with advanced security and sharing capabilities. It is an ''Infrastructure as a Service'' ([[Infrastructure_as_a_service#Infrastructure|IaaS]]), comparable to [[Amazon S3]] online storage service. |
'''Google Storage''' for Developers is a [[Restful|RESTful]] [[online storage]] [[web service]] for storing and accessing your data on [[Google]]'s infrastructure. The service combines the performance and scalability of Google's cloud with advanced security and sharing capabilities. It is an ''Infrastructure as a Service'' ([[Infrastructure_as_a_service#Infrastructure|IaaS]]), comparable to [[Amazon S3]] online storage service. |
||
== |
== Design == |
||
Google Storage (GS) stores objects that are organized into buckets (as S3 does) identified within each bucket by a unique, user-assigned key. All requests are authorized using an [[access control list]] associated with each bucket and object. Bucket names and keys are chosen so that objects are addressable using HTTP [[Uniform Resource Locator|URL]]s: |
|||
* <code><nowiki>http://</nowiki>commondatastorage.googleapis.com/''bucket''/''object''</code> |
|||
* <code><nowiki>http://</nowiki>''bucket''.commondatastorage.googleapis.com/''object''</code> |
|||
== Features == |
|||
* '''Interoperability''' - Google Storage is interoperable with other cloud storage tools and libraries that work with services such as [[Amazon S3]] and [[Eucalyptus_(computing)|Eucalyptus Systems]]. |
|||
* '''Consistency''' - Upload operations to Google Storage are atomic, providing strong read-after-write consistency for all upload operations. |
|||
* '''Access Control''' - Google Storage uses [[access control list]] (ACLs) to manage object and bucket access. An ACL consists of one or more entries, each granting a specific permission to a scope. Permissions define what someone can do with an object or bucket (for example, READ or WRITE). Scopes define who the permission applies to. For example, a specific user or a group of users (such as Google account email addresses, Google Apps domain, public access, etc.) |
|||
* '''Resumable Uploads''' - Google Storage provides a resumable data transfer feature that allows to resume upload operations after a communication failure has interrupted the flow of data. |
|||
== External links == |
|||
*[http://code.google.com/apis/storage/ Official website] |
*[http://code.google.com/apis/storage/ Official website] |
||
Revision as of 14:38, 3 January 2011
Type of site | File hosting service |
|---|---|
| Available in | English |
| Owner | |
| URL | code.google.com/apis/storage |
| Registration | Required |
 |
Google Storage for Developers is a RESTful online storage web service for storing and accessing your data on Google's infrastructure. The service combines the performance and scalability of Google's cloud with advanced security and sharing capabilities. It is an Infrastructure as a Service (IaaS), comparable to Amazon S3 online storage service.
Design
Google Storage (GS) stores objects that are organized into buckets (as S3 does) identified within each bucket by a unique, user-assigned key. All requests are authorized using an access control list associated with each bucket and object. Bucket names and keys are chosen so that objects are addressable using HTTP URLs:
http://commondatastorage.googleapis.com/bucket/objecthttp://bucket.commondatastorage.googleapis.com/object
Features
- Interoperability - Google Storage is interoperable with other cloud storage tools and libraries that work with services such as Amazon S3 and Eucalyptus Systems.
- Consistency - Upload operations to Google Storage are atomic, providing strong read-after-write consistency for all upload operations.
- Access Control - Google Storage uses access control list (ACLs) to manage object and bucket access. An ACL consists of one or more entries, each granting a specific permission to a scope. Permissions define what someone can do with an object or bucket (for example, READ or WRITE). Scopes define who the permission applies to. For example, a specific user or a group of users (such as Google account email addresses, Google Apps domain, public access, etc.)
- Resumable Uploads - Google Storage provides a resumable data transfer feature that allows to resume upload operations after a communication failure has interrupted the flow of data.
