Google Formally Removes Files API

Two years after Google deprecated the Files API, the company has announced that it will formally remove the API on Aug. 5. The Files API enabled apps to read and write blobs to both the App Engine Blobstore storage system and Google Cloud StorageTrack this API. Over time, Google Cloud Storage and the Google Cloud Storage Client Library outpaced the Files API from a feature standpoint, and the Files API diminished in value. Since Google desires that App Engine provide the most up-to-date, feature-rich tech for businesses, Google decided to remove the Files API.

While many developers have migrated away from the Files API since the deprecation announcement in 2013, the formal removal could have hidden consequences for users of other Google services. Older versions of both MapReduce and Pipelines use the Files API. The current versions of both services have progressed beyond the Files API; however, apps that utilize older versions of either service should upgrade to the current version. To determine whether an app uses the Files API, look for a log warning when using the development server for test and development. The warning will contain the text "deprecated."

The suggested migration path away from the Files API is to the Google Cloud Storage Client Library. Google has provided two sets of documentation to help users migrate. One set of docs focuses on apps that use the Files API with Blobstore. The other set of docs concentrates on apps that use the Files API with Google Cloud Storage. Those who need specific assistance can call on an available support package or reach out via the support contact form.

Google ended access to the Files API for new applications in late May. On July 29, the Files API will temporarily shut down for 24 hours. Then, on Aug. 5, the API will permanently shut down. This stepped-down decommissioning approach falls in line with Google's typical deprecation process. For details on the services being shut down, visit the deprecation files.

Be sure to read the next Storage article: Microsoft Makes API Changes to Azure Storage Service

 

Comments (0)