现已推出具有 MongoDB 兼容性的 Firestore 企业版！
了解详情。
與 MongoDB 相容的 Cloud Firestore 位置
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
佈建 Cloud Firestore 資料庫時，您必須選擇位置。為了縮短延遲時間並提高可用性，請將您的資料儲存在需要這些資料的使用者和服務附近的位置。
您也可以視需要在專案中建立多個資料庫，每個資料庫都有自己的位置設定。
請注意，資料庫佈建完成後，就無法變更位置設定。
位置的類型
您可以將與 MongoDB 相容的 Cloud Firestore 資料儲存在多地區位置或單一地區位置。
多區域位置
選取多地區位置，盡可能提高資料庫的可用性和耐用性。
多區域位置由一組定義的區域組成，資料庫的多個副本會儲存在這些區域。每個副本可以是讀寫副本 (包含資料庫中的所有資料)，也可以是見證副本 (不維護完整資料集，但會參與複製作業)。
透過在多個區域之間複製資料，即使整個區域都遺失，資料仍可繼續提供服務。在某個區域內，資料會在各個可用區中複製，因此即使某個可用區發生故障，該區域仍可繼續提供資料。
與 MongoDB 相容的 Cloud Firestore 支援下列多區域位置：
| 多地區名稱 |
多地區說明 |
讀寫地區 |
見證地區 |
eur3 |
歐洲 |
europe-west1 (比利時)、europe-west4 (荷蘭) |
europe-north1 (芬蘭) |
nam5 |
美國 (中部) |
us-central1 (愛荷華州)、us-central2 (奧克拉荷馬州，不公開的 Google Cloud 地區) |
us-east1 (南卡羅來納州) |
nam7 |
美國 (中東部) |
us-central1 (愛荷華州)、us-east4 (北維吉尼亞州) |
us-central2 (奧克拉荷馬州，不公開的 Google Cloud 地區) |
地區位置
單一地區位置是指特定地理位置，例如南卡羅來納州。單一地區位置中的資料會在區域內的多個可用區中複製，所有單一地區位置彼此皆相隔至少 100 英里遠。
如果應用程式容易受到延遲影響，請選取單一地區位置，這樣不僅費用較低，寫入延遲時間也較短，而且還能與其他 Google Cloud 資源共置。
與 MongoDB 相容的 Cloud Firestore 支援下列區域資源位置：
| 地區名稱 | 地區說明 |
|---|
| 北美洲 |
| 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
|
約翰尼斯堡 |
位置服務水準協議
Cloud Firestore 與 MongoDB 相容的服務位置類型，決定了正式發布 (GA) 時的服務水準協議 (SLA) 正常運作時間百分比：
| 涵蓋服務 |
每月正常運作時間百分比 |
| 與 MongoDB 相容的 Cloud Firestore 多區域 |
>= 99.999% |
| 與 MongoDB 相容的 Cloud Firestore 區域 |
>= 99.99% |
位置定價
與 MongoDB 相容的 Cloud Firestore 位置會決定資料庫作業的費用。
如要全面瞭解各區域和區域類型的定價，請參閱「瞭解與 MongoDB 相容的 Cloud Firestore 帳單」。
查看資料庫位置
請使用下列其中一種方法，查看資料庫的位置設定：
後續步驟
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-29 (世界標準時間)。
[null,null,["上次更新時間：2025-08-29 (世界標準時間)。"],[],[],null,["\u003cbr /\u003e\n\nWhen you provision a Cloud Firestore database, you must choose a\n*location* for it. To reduce latency and increase availability, store\nyour data close to the users and services that need it.\n\nYou can optionally [create multiple databases](/docs/firestore/manage-databases) in your\nproject, each with its own location setting.\n\nBe aware that once you provision a database, you cannot change its\nlocation setting.\n\nTypes of locations\n\nYou can store your Cloud Firestore with MongoDB compatibility data in a\n[*multi-region* location](#location-mr) or a [*regional* location](#location-r).\n\nMulti-region locations\n\nSelect a multi-region location to maximize the availability and\ndurability of your database.\n\nA multi-region location consists of a defined set of\n[regions](https://cloud.google.com/docs/geography-and-regions#regions_and_zones) where multiple replicas of the database\nare stored. Each replica is either a read-write replica which contains all of the\ndata in the database or a witness replica which does not maintain a full set of\ndata but participates in replication.\n\nBy replicating the data between multiple regions, data\ncan continue to be served even with the loss of an entire\nregion. Within a region, data is replicated across\n[zones](https://cloud.google.com/docs/geography-and-regions#regions_and_zones) so that data can continue to be served\nwithin that region even with the loss of a zone.\n\nCloud Firestore with MongoDB compatibility supports the following multi-region locations:\n\n| Multi-region name | Multi-region description | Read-Write regions | Witness region |\n|-------------------|----------------------------------|------------------------------------------------------------------------------|--------------------------------------------------------|\n| `eur3` | Europe | `europe-west1` (Belgium), `europe-west4` (Netherlands) | `europe-north1` (Finland) |\n| `nam5` | United States (Central) | `us-central1` (Iowa), `us-central2` (Oklahoma---private Google Cloud region) | `us-east1` (South Carolina) |\n| `nam7` | United States (Central and East) | `us-central1` (Iowa), `us-east4` (Northern Virginia) | `us-central2` (Oklahoma---private Google Cloud region) |\n\nRegional locations\n\nA regional location is a specific geographic place, such as South Carolina. Data\nin a regional location is replicated in multiple zones within a\n[region](https://cloud.google.com/docs/geography-and-regions#regional_resources). All regional locations are separated from other regional\nlocations by at least 100 miles.\n\nSelect a regional location for lower costs, for lower write latency if your\napplication is sensitive to latency, or for\n[co-location with other Google Cloud resources](https://cloud.google.com/about/locations/#products-available-by-region).\n\nCloud Firestore with MongoDB compatibility supports the following regional resource locations:\n\n| | Region name | Region description |\n|---|---------------------------|--------------------|\n| **North America** |||\n| | `us-west1` | Oregon |\n| | `us-west2` | Los Angeles |\n| | `us-west3` | Salt Lake City |\n| | `us-west4` | Las Vegas |\n| | `us-central1` | Iowa |\n| | `northamerica-northeast1` | Montréal |\n| | `northamerica-northeast2` | Toronto |\n| | `northamerica-south1` | Queretaro |\n| | `us-east1` | South Carolina |\n| | `us-east4` | Northern Virginia |\n| | `us-east5` | Columbus |\n| | `us-south1` | Dallas |\n| **South America** |||\n| | `southamerica-west1` | Santiago |\n| | `southamerica-east1` | São Paulo |\n| **Europe** |||\n| | `europe-west2` | London |\n| | `europe-west1` | Belgium |\n| | `europe-west4` | Netherlands |\n| | `europe-west8` | Milan |\n| | `europe-southwest1` | Madrid |\n| | `europe-west9` | Paris |\n| | `europe-west12` | Turin |\n| | `europe-west10` | Berlin |\n| | `europe-west3` | Frankfurt |\n| | `europe-north1` | Finland |\n| | `europe-north2` | Stockholm |\n| | `europe-central2` | Warsaw |\n| | `europe-west6` | Zürich |\n| **Middle East** |||\n| | `me-central1` | Doha |\n| | `me-central2` | Dammam |\n| | `me-west1` | Tel Aviv |\n| **Asia** |||\n| | `asia-south1` | Mumbai |\n| | `asia-south2` | Delhi |\n| | `asia-southeast1` | Singapore |\n| | `asia-southeast2` | Jakarta |\n| | `asia-east2` | Hong Kong |\n| | `asia-east1` | Taiwan |\n| | `asia-northeast1` | Tokyo |\n| | `asia-northeast2` | Osaka |\n| | `asia-northeast3` | Seoul |\n| **Australia** |||\n| | `australia-southeast1` | Sydney |\n| | `australia-southeast2` | Melbourne |\n| **Africa** |||\n| | `africa-south1` | Johannesburg |\n\nLocation SLA\n\nYour Cloud Firestore with MongoDB compatibility location type determines the\n[Service Level Agreement (SLA)](/terms)\nuptime percentage at General Availability (GA):\n\n| Covered service | Monthly uptime percentage |\n|---------------------------------------------------------|---------------------------|\n| Cloud Firestore with MongoDB compatibility Multi-Region | \\\u003e= 99.999% |\n| Cloud Firestore with MongoDB compatibility Regional | \\\u003e= 99.99% |\n\nLocation pricing\n\nYour Cloud Firestore with MongoDB compatibility location determines the cost of database\noperations.\n\nFor a comprehensive explanation of pricing per region and per region type,\nsee [Understand Cloud Firestore with MongoDB compatibility billing](https://firebase.google.com/pricing).\n\nView the location of your databases\n\nUse one of the following methods to view the location setting for your databases:\n\n- Run the [`gcloud firestore databases list`](https://cloud.google.com//sdk/gcloud/reference/firestore/databases/list)\n command.\n\n- Open the\n [database list](https://console.cloud.google.com/firestore/databases) in the Google Cloud console.\n The location for each database is in the location column.\n\nNext steps\n\n- To create a Cloud Firestore with MongoDB compatibility database in a specific location, see\n [Create and manage databases](/docs/firestore/manage-databases)\n\n- For more information about building applications to meet your latency,\n availability, and durability requirements, refer to\n [Geography and Regions](https://cloud.google.com/docs/geography-and-regions#multi-regional_resources)."]]
