I would be surprised if Google used some other infrastructure for Drive vs Cloud Storage (I think Drive is built on Cloud Storage), but since Drive is essentially an app built on Cloud Storage, the buckets and keys used are not exposed to Drive usage.Īdditionally, other folks seems to say the same thing as I am. It's unlikely you can get the bucket and key id for the data you have stored in Google Drive.

This illustrates the primary difference between the two APIs: Cloud Storage enables developers to store their application data in the Google cloud (and they’re responsible for the storage their app consumes), whereas in Drive, users allow apps to interact with the user’s private storage and content.įor an overview of Google storage options, including a video explaining the differences between the options, see Storing Your Data. Google Cloud Storage can also be used for online archives, backup replacement, and so on. For example, a developer could store and host media and other static assets for a web game in Google Cloud Storage. Google Cloud Storage is intended to be accessed primarily through its API and provides all the functionality necessary for developers to use it as a backing store for their own applications. For instance, a user could install a Drive app to edit images or fax PDF files, and could create and open files with those apps directly in Google Drive. These apps enhance the user experience by allowing users to interact with their data in novel ways.

The Google Drive SDK works together with the Google Drive UI and the Chrome Web Store to create an ecosystem of apps that can be installed into Google Drive. Both services allow programmatic access to their functionality, but the goals of the APIs are quite different. Google provides two different storage services: Google Cloud Storage, and Google Drive. Google Storage and Google Drive - which storage API should my application use?

Cyberduck linux