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. This location setting is your project's
default Google Cloud Platform (GCP) resource location
.
Note that your default GCP resource location might have been previously set,
either during project creation or when setting up another service that requires
a location setting (see below).
Default GCP resource location
Several services available for your app require a location setting, called your
project's
default Google Cloud Platform (GCP) resource location
. This location
is where your data is stored for GCP services that require a location setting.
The following products share the same default GCP resource location:
Cloud Firestore
Note that your default GCP resource location does
not
apply to
Firebase Realtime Database
.
Cloud Storage
Note that your default GCP resource location only applies to your
default
Cloud Storage
bucket.
If you're on the Blaze plan, you can create multiple
buckets, each with its own
location
.
Google App Engine (GAE) app
If you set up an
App Engine app
, its location
shares your default GCP resource location.
Note that if you use Cloud Scheduler (for example, to run
scheduled functions
), you're required to
have an App Engine app in your project.
Types of locations
You can store your Cloud Firestore data in a
multi-region
location
or a
regional
location
.
Note that if you already have an App Engine app with a location of either
us-central
or
europe-west
, your Cloud Firestore database will be
considered
multi-regional
.
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.
Firebase supports the following multi-region GCP resource 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
|
us-central1
(Iowa),
us-central2
(Oklahoma?private GCP region)
|
us-east1
(South Carolina)
|
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 GCP resources
.
Firebase supports the following regional GCP resource locations:
| Region Name
| Region Description
|
North America
|
| us-west1
| Oregon
|
| us-west2
| Los Angeles
|
| us-west3
| Salt Lake City
|
| us-west4
| Las Vegas
|
|
us-central1
|
Iowa
|
| northamerica-northeast1
| Montreal
|
|
northamerica-northeast2
|
Toronto
|
| us-east1
| South Carolina
|
| us-east4
| Northern Virginia
|
|
us-east5
This location does not support Cloud Storage for Firebase.
If you plan to use Cloud Storage for Firebase, you should choose a
different location.
|
Columbus
|
South America
|
|
southamerica-west1
This location does not support Cloud Storage for Firebase.
If you plan to use Cloud Storage for Firebase, you should choose a
different location.
|
Santiago
|
| southamerica-east1
| Sao Paulo
|
Europe
|
| europe-west2
| London
|
|
europe-west1
|
Belgium
|
|
europe-west4
|
Netherlands
|
|
europe-west8
This location does not support Cloud Storage for Firebase.
If you plan to use Cloud Storage for Firebase, you should choose a
different location.
|
Milan
|
|
europe-southwest1
This location does not support Cloud Storage for Firebase.
If you plan to use Cloud Storage for Firebase, you should choose a
different location.
|
Madrid
|
|
europe-west9
|
Paris
|
|
europe-west12
This location does not support Cloud Storage for Firebase.
If you plan to use Cloud Storage for Firebase, you should choose a
different location.
|
Turin
|
|
europe-west10
This location does not support Cloud Storage for Firebase.
If you plan to use Cloud Storage for Firebase, you should choose a
different location.
|
Berlin
|
| europe-west3
| Frankfurt
|
|
europe-north1
This location does not support Cloud Storage for Firebase.
If you plan to use Cloud Storage for Firebase, you should choose a
different location.
|
Finland
|
| europe-central2
| Warsaw
|
| europe-west6
| Zurich
|
Middle East
|
|
me-central1
|
Doha
|
|
me-central2
|
Dammam
|
|
me-west1
|
Tel Aviv
|
Asia
|
| asia-south1
| Mumbai
|
|
asia-south2
This location does not support Cloud Storage for Firebase.
If you plan to use Cloud Storage for Firebase, you should choose a
different location.
|
Delhi
|
| asia-southeast1
| Singapore
|
| asia-southeast2
| Jakarta
|
| asia-east2
| Hong Kong
|
| asia-east1
| Taiwan
|
| asia-northeast1
| Tokyo
|
| asia-northeast2
| Osaka
|
| asia-northeast3
| Seoul
|
Australia
|
| australia-southeast1
| Sydney
|
|
australia-southeast2
This location does not support Cloud Storage for Firebase.
If you plan to use Cloud Storage for Firebase, you should choose a
different location.
|
Melbourne
|
Africa
|
|
africa-south1
This location does not support Cloud Storage for Firebase.
If you plan to use Cloud Storage for Firebase, you should choose a
different location.
|
Johannesburg
|
Location SLA
Your Cloud Firestore location type determines the
Service Level Agreement (SLA)
uptime percentage:
Covered Service
|
Monthly Uptime Percentage
|
Cloud Firestore Multi-Region
|
>= 99.999%
|
Cloud Firestore Regional
|
>= 99.99%
|
Location Pricing
Your Cloud Firestore location determines the cost of database
operations.
For a comprehensive explanation of pricing per region and per region type,
see
Understand Cloud Firestore billing
.
View the location of your databases
In the Firebase console, go to your
Project settings
.
Next steps
- For more information about building applications to meet your latency,
availability, and durability requirements, refer to
Geography and Regions
.