快速的 NoSQL 資料庫支援開放式 API 及任何規模
使用 Azure Cosmos DB 快速輕鬆地開發應用程式，這是一種支援 NoSQL 和關係工作負載的完全受控和無伺服器分散式資料庫。提供 NoSQL 資料的速度和可用性、自動化和立即擴縮性以及開放來源 PostgreSQL、MongoDB 和 Cassandra 的支援。Azure Cosmos DB 為從開發/測試到生產等任何規模的應用程式提供具有成本效益的計價模式
探索定價選項
套用篩選以根據您的需求自訂定價選項。
Prices are estimates only and are not intended as actual price quotes. Actual pricing may vary depending on the type of agreement entered with Microsoft, date of purchase, and the currency exchange rate. Prices are calculated based on US dollars and converted using London closing spot rates that are captured in the two business days prior to the last business day of the previous month end. If the two business days prior to the end of the month fall on a bank holiday in major markets, the rate setting day is generally the day immediately preceding the two business days. This rate applies to all transactions during the upcoming month. Sign in to the Azure pricing calculator to see pricing based on your current program/offer with Microsoft. Contact an Azure sales specialist for more information on pricing or to request a price quote. See frequently asked questions about Azure pricing. Learn how you can save on your dynamic workloads with savings plan for databases.
美國政府機構有資格透過授權解決方案提供者購買 Azure Government 服務，無須預先支付費用；亦可直接透過隨用隨付線上訂用帳戶購買。
重要 - 以 R$ 表示的價格僅供參考；這是國際交易，因此最終價格需視匯率與是否內含 IOF 稅而定，而且不會發行 eNF。
美國政府機構有資格透過授權解決方案提供者購買 Azure Government 服務，無須預先支付費用；亦可直接透過隨用隨付線上訂用帳戶購買。
重要 - 以 R$ 表示的價格僅供參考；這是國際交易，因此最終價格需視匯率與是否內含 IOF 稅而定，而且不會發行 eNF。
Azure Cosmos DB 定價模型
Azure Cosmos DB 針對三種不同使用類型計費：計算、儲存體和頻寬。下方的索引標籤更詳細地描述每個計算價格模型，及其伴隨的儲存體和頻寬價格模型。
一旦選擇了計算定價模型和 API，就無法變更。
計算定價:
要求單位 (輸送量): Azure Cosmos DB 使用每秒測量的要求單位 (RU/秒) 計費。要求單位是用來處理資料庫作業的計算、記憶體和 IO 的 Proxy，會針對您的 Azure Cosmos DB 帳戶所有選取的 Azure 區域計費。
輸送量選項包括: 標準佈建的輸送量、自動調整佈建的輸送量和無伺服器。
適用的 API: NoSQL、MongoDB (RU)、Cassandra、Gremlin 和 Table。
虛擬核心: Azure Cosmos DB 會根據每個節點處理資料庫作業的虛擬核心數 (計算和記憶體) 計費，並根據佈建的節點大小和數目計費。
Available APIs: PostgreSQL, MongoDB (vCore), Garnet Cache.
儲存體定價:
已使用的儲存體: Azure Cosmos DB 會根據每個區域內的容器/集合/資料表/圖形所使用的儲存體，以 GB 的部分容量計費。已使用的儲存體包含所有異動和分析資料與索引，以及備份。
適用的 API: NoSQL、MongoDB (RU)、Cassandra、Gremlin 和 Table。
磁碟儲存體: Azure Cosmos DB 會根據為每個節點佈建的磁碟依儲存大小計費。
Applicable APIs: PostgreSQL, MongoDB (vCore), Garnet Cache.
頻寬定價:
資料輸出: Azure 會根據輸出 Azure 雲端或跨區域或可用性區域傳輸 Azure WAN 的資料計費。
適用的 API: 全部。
Azure Cosmos DB Garnet Cache is a high-performance, scalable, distributed cache designed to accelerate data access and reduce latency for applications. It is best for workloads that require:
- Consistent low latency for reads and writes at scale
- High throughput, low latency vector searches for AI driven workloads
- Resilient and highly available caching
- Rich and extensible APIs with support for the RESP protocol and Redis commands
Learn more about Azure Cosmos DB Garnet Cache.
Garnet Cache Cluster
Each Azure Cosmos DB Garnet Cache cluster has one or more nodes. You can distribute data across multiple nodes in a cluster by adding shards. As the performance needs of your workload grow, you can vertically scale by choosing a larger SKU or horizontally scale by adding additional shards to your cluster.
High availability (HA) avoids cache downtime by maintaining replicas. Azure Cosmos DB Garnet Cache allows you configure your replication factor to control how many nodes (primary and replicas) are provisioned for each shard.
Azure Cosmos DB Garnet Cache uses Premium SSD managed disks to store snapshots when data persistence is enabled. Each node in the cluster has its own attached disk, and the size of the disk scales based on the amount of data available for the chosen VM SKU. When data persistence is enabled, both primary and replica nodes have attached disks.
General Purpose v6-series
Pricing for the Ds_v6 series.
| VM SKU | vCPUs per Node | Total RAM per Node* | Compute Price per Node | Disk Price per Node** |
|---|---|---|---|---|
| D2 | 2 | 8 GiB | $- | $- |
| D4 | 4 | 16 GiB | $- | $- |
| D8 | 8 | 32 GiB | $- | $- |
| D16 | 16 | 64 GiB | $- | $- |
| D32 | 32 | 128 GiB | $- | $- |
| D48 | 48 | 192 GiB | $- | $- |
| D64 | 64 | 256 GiB | $- | $- |
| D96 | 96 | 384 GiB | $- | $- |
| D128 | 128 | 512 GiB | $- | $- |
| D192 | 192 | 768 GiB | $- | $- |
* There is a variable amount of cacheable RAM due operational overhead. Plan for a buffer when determining the storage needs of your cluster and monitor using the Azure Portal.
** Applicable when data persistence is enabled
General Purpose
Pricing for the Ds_v5, Das_v5, Ds_v4 series is uniform based on the number of vCores regardless of the series chosen. For example, Standard_D32s_v5, Standard_D32as_v5, and Standard_D32s_v4 are all priced at the same D32 rate.
| VM SKU | vCPUs per Node | Total RAM per Node* | Compute Price per Node | Disk Price per Node** |
|---|---|---|---|---|
| D2 | 2 | 8 GiB | $- | $- |
| D4 | 4 | 16 GiB | $- | $- |
| D8 | 8 | 32 GiB | $- | $- |
| D16 | 16 | 64 GiB | $- | $- |
| D32 | 32 | 128 GiB | $- | $- |
| D48 | 48 | 192 GiB | $- | $- |
| D64 | 64 | 256 GiB | $- | $- |
| D96 | 96 | 384 GiB | $- | $- |
* There is a variable amount of cacheable RAM due operational overhead. Plan for a buffer when determining the storage needs of your cluster and monitor using the Azure Portal.
** Applicable when data persistence is enabled
General Purpose Burstable
Pricing for the Bls_v2, Bals_v2 series is uniform based on the number of vCores regardless of the series chosen. For example, Standard_B2ls_v2 and Standard_B2als_v2 are all priced at the same B2 rate.
| VM SKU | vCPUs per Node | Total RAM per Node* | Compute Price per Node | Disk Price per Node** |
|---|---|---|---|---|
| B2 | 2 | 4 GiB | $- | $- |
* There is a variable amount of cacheable RAM due operational overhead. Plan for a buffer when determining the storage needs of your cluster and monitor using the Azure Portal.
** Applicable when data persistence is enabled
Memory Optimized v6-series
Pricing for the Es_v6 series.
| VM SKU | vCPUs per Node | Total RAM per Node* | Compute Price per Node | Disk Price per Node** |
|---|---|---|---|---|
| E2 | 2 | 16 GiB | $- | $- |
| E4 | 4 | 32 GiB | $- | $- |
| E8 | 8 | 64 GiB | $- | $- |
| E16 | 16 | 128 GiB | $- | $- |
| E20 | 20 | 160 GiB | $- | $- |
| E32 | 32 | 256 GiB | $- | $- |
| E48 | 48 | 384 GiB | $- | $- |
| E64 | 64 | 512 GiB | $- | $- |
| E96 | 96 | 768 GiB | $- | $- |
| E128 | 128 | 1,024 GiB | $- | $- |
* There is a variable amount of cacheable RAM due operational overhead. Plan for a buffer when determining the storage needs of your cluster and monitor using the Azure Portal.
** Applicable when data persistence is enabled
Memory Optimized
Pricing for the Es_v5, Eas_v5, Es_v4 series is uniform based on the number of vCores regardless of the series chosen. For example, Standard_E32s_v5, Standard_E32as_v5, and Standard_E32s_v4 are all priced at the same E32 rate.
| VM SKU | vCPUs per Node | Total RAM per Node* | Compute Price per Node | Disk Price per Node** |
|---|---|---|---|---|
| E2 | 2 | 16 GiB | $- | $- |
| E4 | 4 | 32 GiB | $- | $- |
| E8 | 8 | 64 GiB | $- | $- |
| E16 | 16 | 128 GiB | $- | $- |
| E20 | 20 | 160 GiB | $- | $- |
| E32 | 32 | 256 GiB | $- | $- |
| E48 | 48 | 384 GiB | $- | $- |
| E64 | 64 | 512 GiB | $- | $- |
| E96 | 96 | 672 GiB | $- | $- |
* There is a variable amount of cacheable RAM due operational overhead. Plan for a buffer when determining the storage needs of your cluster and monitor using the Azure Portal.
** Applicable when data persistence is enabled
Compute Optimized v6-series
Pricing for the Fas_v6 series.
| VM SKU | vCPUs per Node | Total RAM per Node* | Compute Price per Node | Disk Price per Node** |
|---|---|---|---|---|
| F2 | 2 | 8 GiB | $- | $- |
| F4 | 4 | 16 GiB | $- | $- |
| F8 | 8 | 32 GiB | $- | $- |
| F16 | 16 | 64 GiB | $- | $- |
| F32 | 32 | 128 GiB | $- | $- |
| F48 | 48 | 192 GiB | $- | $- |
| F64 | 64 | 256 GiB | $- | $- |
* There is a variable amount of cacheable RAM due operational overhead. Plan for a buffer when determining the storage needs of your cluster and monitor using the Azure Portal.
** Applicable when data persistence is enabled
Storage Optimized
Pricing for the Ls_v3 and Ls_v4 series is uniform based on the number of vCores regardless of the series chosen. For example, Standard_L32s_v3 and Standard_L32s_v4 are both priced at the same L32 rate.
| VM SKU | vCPUs per Node | Total RAM per Node* | Local NVMe Storage | Compute Price per Node | Disk Price per Node** |
|---|---|---|---|---|---|
| L2 | 2 | 16 GiB | 480GB | $- | $- |
| L4 | 4 | 32 GiB | 960GB | $- | $- |
| L8 | 8 | 64 GiB | 1,920GB | $- | $- |
| L16 | 16 | 128 GiB | 3,840GB | $- | $- |
| L32 | 32 | 256 GiB | 7,680GB | $- | $- |
| L48 | 48 | 384 GiB | 11,520GB | $- | $- |
| L64 | 64 | 512 GiB | 15,360GB | $- | $- |
| L80 | 80 | 640 GiB | 19,200GB | $- | $- |
| L96 | 96 | 768 GiB | 23,040GB | $- | $- |
* There is a variable amount of cacheable RAM due operational overhead. Plan for a buffer when determining the storage needs of your cluster and monitor using the Azure Portal.
** Applicable when data persistence is enabled
頻寬
Azure Networking bills for data that egresses the Azure cloud to a destination on the internet or transits the Azure WAN between regions, see Azure Networking Bandwidth Pricing.Azure 定價與購買選項
其他資源
Azure Cosmos DB
深入了解 Azure Cosmos DB 的功能。
定價計算機
預估您使用任何 Azure 產品組合的預期每月費用。
SLA
檢閱 Azure Cosmos DB 的服務等級協定。
文件
檢閱技術教學課程、影片和更多 Azure Cosmos DB 資源。
與銷售專員洽談，取得 Azure 定價的逐步解說。了解您雲端解決方案的定價。
取得免費的雲端服務，以及可於 30 天內用來探索 Azure 的 $200 點數。