Go 1.11 has reached end of support
and will be
deprecated
on January 31, 2026. After deprecation, you won't be able to deploy Go 1.11
applications, even if your organization previously used an organization policy to
re-enable deployments of legacy runtimes. Your existing Go
1.11 applications will continue to run and receive traffic after their
deprecation date. We
recommend that you
migrate to the latest supported version of Go.
Understanding Data and File Storage
Stay organized with collections
Save and categorize content based on your preferences.
To store data and files on App Engine, you can use Google Cloud services
or any other storage service that is supported by your language and is
accessible from your App Engine instance. Third-party databases
can be hosted on another cloud provider,
hosted on premises, or managed by a third-party vendor.
Google Cloud storage services
For App Engine apps running in the App Engine, we recommend
one of the following Google Cloud storage services:
See a complete list of the Google Cloud storage products on the
Cloud Storage Products page.
Other cloud providers
App Engine apps can connect to external databases that are hosted on
other public clouds as long as those database servers and your firewall are
configured properly to accept connections. Your App Engine app connects
over the Internet using that external service's public IP address.
Databases managed by a third-party vendor
There are many vendors offering managed database services such as
mLab for MongoDB, Redis Labs offers hosted
Redis caching. These vendors handle
hosting, configuration, and maintenance of databases. App Engine can
connect to these external services over the Internet, in the same way as other
public clouds by using that service's public IP address.
On premises
If you have existing on-premises databases that you want to make accessible to
your App Engine app, you can either configure your internal
network and firewall to give the database a public IP address or connect using a
VPN.
Setting up
Cloud VPN allows your App Engine
app to access your on-premises network without directly exposing the
database server to the public internet. Because App Engine and
Compute Engine use the same networking infrastructure, you can use the VPN
connection to establish a connection between the App Engine app
and your on-premises database using the database server's internal IP address.
Production considerations
App Engine can be configured to automatically scale your application
horizontally
based on various metrics. Unlike web applications, databases often
require non-trivial changes to respond to scale. In production applications,
App Engine can quickly overwhelm a database during traffic spikes. You
should take the anticipated average traffic load and load during spikes into
consideration when configuring and deploying databases.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-29 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eApp Engine allows you to store data and files using various Google Cloud storage services, such as Firestore in Datastore mode, Cloud SQL for MySQL or PostgreSQL, and Cloud Storage for files.\u003c/p\u003e\n"],["\u003cp\u003eYou can connect App Engine apps to external databases hosted on other public clouds, provided the database servers and firewalls are configured to accept connections via public IP addresses.\u003c/p\u003e\n"],["\u003cp\u003eApp Engine can integrate with third-party managed database services, like mLab for MongoDB or Redis Labs for Redis caching, connecting via the service's public IP address.\u003c/p\u003e\n"],["\u003cp\u003eOn-premises databases can be accessed by App Engine apps by configuring the internal network to provide the database with a public IP address, or through a VPN connection using Cloud VPN for enhanced security.\u003c/p\u003e\n"],["\u003cp\u003eWhen deploying databases for production with App Engine, it is crucial to account for average traffic load and potential spikes, as databases may require significant adjustments to scale effectively.\u003c/p\u003e\n"]]],[],null,["# Understanding Data and File Storage\n\nTo store data and files on App Engine, you can use Google Cloud services\nor any other storage service that is supported by your language and is\naccessible from your App Engine instance. Third-party databases\ncan be hosted on another cloud provider,\nhosted on premises, or managed by a third-party vendor.\n\nGoogle Cloud storage services\n-----------------------------\n\nFor App Engine apps running in the App Engine, we recommend\none of the following Google Cloud storage services:\n\n\n- [Firestore in Datastore mode](/appengine/docs/legacy/standard/go111/using-cloud-datastore) to store data in a NoSQL database\n\n\u003c!-- --\u003e\n\n- [Cloud SQL for MySQL](/sql/docs/mysql/connect-app-engine)\n to store data in a MySQL database\n\n- [Cloud SQL for PostgreSQL](/sql/docs/postgres/connect-app-engine)\n to store data in a PostgreSQL database\n\n- [Cloud Storage](/appengine/docs/legacy/standard/go111/using-cloud-storage)\n to read and write files in the runtime environment, as well as\n [store and serve static files](/appengine/docs/legacy/standard/go111/serving-static-files),\n such as movies or images or other static content\n\n\u003cbr /\u003e\n\nSee a complete list of the Google Cloud storage products on the\n[Cloud Storage Products page](/products/storage).\n\nOther cloud providers\n---------------------\n\nApp Engine apps can connect to external databases that are hosted on\nother public clouds as long as those database servers and your firewall are\nconfigured properly to accept connections. Your App Engine app connects\nover the Internet using that external service's public IP address.\n\nDatabases managed by a third-party vendor\n-----------------------------------------\n\nThere are many vendors offering managed database services such as\n[mLab](/mongodb) for MongoDB, Redis Labs offers hosted\n[Redis caching](https://redislabs.com/redis-enterprise/cloud/). These vendors handle\nhosting, configuration, and maintenance of databases. App Engine can\nconnect to these external services over the Internet, in the same way as other\npublic clouds by using that service's public IP address.\n\nOn premises\n-----------\n\nIf you have existing on-premises databases that you want to make accessible to\nyour App Engine app, you can either configure your internal\nnetwork and firewall to give the database a public IP address or connect using a\nVPN.\nSetting up [Cloud VPN](/network-connectivity/docs/vpn) allows your App Engine app to access your on-premises network without directly exposing the database server to the public internet. Because App Engine and Compute Engine use the same networking infrastructure, you can use the VPN connection to establish a connection between the App Engine app and your on-premises database using the database server's internal IP address.\n\nProduction considerations\n-------------------------\n\nApp Engine can be configured to automatically scale your application\n[horizontally](https://wikipedia.org/wiki/Scalability#Horizontal_and_vertical_scaling)\nbased on various metrics. Unlike web applications, databases often\nrequire non-trivial changes to respond to scale. In production applications,\nApp Engine can quickly overwhelm a database during traffic spikes. You\nshould take the anticipated average traffic load and load during spikes into\nconsideration when configuring and deploying databases."]]
