When you provision a Cloud Firestore database, you must choose a location for it. To reduce latency and increase availability, store your data close to the users and services that need it.
You can optionally create multiple databases in your project, each with its own location setting.
Be aware that once you provision a database, you cannot change its location setting.
Types of locations
You can store your Cloud Firestore with MongoDB compatibility data in a multi-region location or a regional location .
Multi-region locations
Select a multi-region location to maximize the availability and durability of your database.
A multi-region location consists of a defined set of regions where multiple replicas of the database are stored. Each replica is either a read-write replica which contains all of the data in the database or a witness replica which does not maintain a full set of data but participates in replication.
By replicating the data between multiple regions, data can continue to be served even with the loss of an entire region. Within a region, data is replicated across zones so that data can continue to be served within that region even with the loss of a zone.
Cloud Firestore with MongoDB compatibility supports the following multi-region locations:
| Multi-region name | Multi-region description | Read-Write regions | Witness region |
|---|---|---|---|
eur3
|
Europe | europe-west1
(Belgium), europe-west4
(Netherlands) |
europe-north1
(Finland) |
nam5
|
United States (Central) | us-central1
(Iowa), us-central2
(Oklahoma—private Google Cloud
region) |
us-east1
(South Carolina) |
nam7
|
United States (Central and East) | us-central1
(Iowa), us-east4
(Northern Virginia) |
us-central2
(Oklahoma—private Google Cloud
region) |
Regional locations
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 . All regional locations are separated from other regional locations by at least 100 miles.
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 resources .
Cloud Firestore with MongoDB compatibility supports the following regional resource locations:
us-west1
us-west2
us-west3
us-west4
us-central1
northamerica-northeast1
northamerica-northeast2
northamerica-south1
us-east1
us-east4
us-east5
us-south1
southamerica-west1
southamerica-east1
europe-west2
europe-west1
europe-west4
europe-west8
europe-southwest1
europe-west9
europe-west12
europe-west10
europe-west3
europe-north1
europe-north2
europe-central2
europe-west6
me-central1
me-central2
me-west1
asia-south1
asia-south2
asia-southeast1
asia-southeast2
asia-east2
asia-east1
asia-northeast1
asia-northeast2
asia-northeast3
australia-southeast1
australia-southeast2
africa-south1
Location SLA
Your Cloud Firestore with MongoDB compatibility location type determines the Service Level Agreement (SLA) uptime percentage at General Availability (GA):
| Covered service | Monthly uptime percentage |
|---|---|
| Cloud Firestore with MongoDB compatibility Multi-Region | >= 99.999% |
| Cloud Firestore with MongoDB compatibility Regional | >= 99.99% |
Location pricing
Your Cloud Firestore with MongoDB compatibility location determines the cost of database operations.
For a comprehensive explanation of pricing per region and per region type, see Understand Cloud Firestore with MongoDB compatibility billing .
View the location of your databases
Use one of the following methods to view the location setting for your databases:
-
Run the
gcloud firestore databases listcommand. -
Open the database list in the Google Cloud console. The location for each database is in the location column.
Next steps
-
To create a Cloud Firestore with MongoDB compatibility database in a specific location, see Create and manage databases
-
For more information about building applications to meet your latency, availability, and durability requirements, refer to Geography and Regions .
