Before you use Cloud Firestore, you must choose a location for your database. To reduce latency and increase availability, store your data close to the users and services that need it.
Types of locations
You can store your Cloud Firestore data in a multi-region location or a regional location.
Select a multi-region location to maximize the availability and durability of your database. Multi-region locations can withstand the loss of entire regions and maintain availability without losing data.
The following multi-region locations are available for Cloud Firestore:
|Multi-Region Name||Multi-Region Description|
A regional location is a specific geographic place, such as South Carolina. Data in a regional location is replicated in multiple zones within a region.
Select a regional location for lower costs, for lower write latency if your application is sensitive to latency, or for co-location with other Google Cloud Platform resources.
The following regional locations are available:
|Region Name||Region Description|
All regional locations are separated from other regional locations by at least 100 miles.
Project location setting
The location setting of your project is shared by the following products:
- Cloud Firestore
- App Engine
This choice sets the location of your default Cloud Storage bucket, though you may create buckets in other locations.
Setting the location in one product also sets the location for the other. Once set, you cannot change your project's location setting.
Viewing the location setting of your projectUse one of the following methods to find out which location you selected for your project:
gcloud app describecommand.
If you have an active App Engine app, open the App Engine Dashboard in the Google Cloud Platform Console. The location information is in the upper right-hand corner of the dashboard and it applies to both App Engine and Cloud Firestore.
- To create a Cloud Firestore database in specific location, see one of the Cloud Firestore quickstarts.
- For more information about building applications to meet your latency, availability and durability requirements, see Geography and Regions.