适用于任何规模的带有开放 API 的快速 NoSQL 数据库
使用 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 政府服务（无需预付定金），或者可直接通过即用即付在线订阅购买。
重要提示 - 该价格 (R$) 只是一个参考；这是一项国际交易，最终价格受汇率和所含 IOF 税的影响。不会发布 eNF。
美国政府实体有资格从授权解决方案提供商处购买 Azure 政府服务（无需预付定金），或者可直接通过即用即付在线订阅购买。
重要提示 - 该价格 (R$) 只是一个参考；这是一项国际交易，最终价格受汇率和所含 IOF 税的影响。不会发布 eNF。
Azure Cosmos DB 定价模型
Azure Cosmos DB 针对三种不同类型的使用计费: 计算、存储和带宽。下面的选项卡更详细地描述了每个计算定价模型，及该模型随附的存储和带宽定价模型。
选择计算定价模式和 API 后，将无法更改它们。
计算定价:
请求单位(吞吐量): Azure Cosmos DB 使用每秒测量的请求单位(RU/s)进行计费。请求单位代表用于处理数据库操作的计算、内存和 IO，并在你的 Azure Cosmos DB 帐户的所有选定 Azure 区域中计费。
吞吐量选项包括: 标准预配吞吐量、自动缩放预配吞吐量和无服务器。
适用的 API: NoSQL、MongoDB (RU)、Cassandra、Gremlin 和 Table。
vCore: Azure Cosmos DB 对每个节点中用于处理数据库操作的 vCore (计算和内存)计费，计费依据为预配节点的大小和数目。
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 | 480 GB | $- | $- |
| L4 | 4 | 32 GiB | 960 GB | $- | $- |
| L8 | 8 | 64 GiB | 1,920 GB | $- | $- |
| L16 | 16 | 128 GiB | 3,840 GB | $- | $- |
| L32 | 32 | 256 GiB | 7,680 GB | $- | $- |
| L48 | 48 | 384 GiB | 11,520 GB | $- | $- |
| L64 | 64 | 512 GiB | 15,360 GB | $- | $- |
| L80 | 80 | 640 GiB | 19,200 GB | $- | $- |
| L96 | 96 | 768 GiB | 23,040 GB | $- | $- |
* 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 定价情况。了解你的云解决方案的定价。
获取免费云服务和价值 $200 的赠金来探索 Azure 30 天。