Are there billing differences between the RU and vCore architectures in Azure Cosmos DB for MongoDB?
在 Azure Cosmos DB for MongoDB 中的 RU 与 vCore 体系结构之间是否存在计费差异？
The RU and vCore services have different architectures with important billing differences.
The RU service variant is a multitenant service that instantly allocates resources to your workload, aligning with storage and throughput requirements. Throughput for this service is based on request units. This service is optimized for users who prefer to pay fixed (standard provisioned throughput) or variable (autoscale) fees corresponding to Request Units (RUs) and consumed storage. Actual RU charges depend on the selected model: provisioned throughput (standard or autoscale) or serverless.
The vCore service variant creates dedicated instances that utilize preset CPU, memory, and storage resources, which can dynamically scale to suit your needs. This service is optimized for users who prefer to pay a consistent flat fee based on compute (CPU, memory, and the number of nodes) and storage.
RU 和 vCore 服务具有不同的体系结构，在计费方面存在重大差异。
RU 服务变体是一个多租户服务，可立即将资源分配给工作负载，以与存储和吞吐量要求保持一致。 此服务的吞吐量基于请求单位。 此服务针对更愿意根据请求单位 (RU) 和消耗的存储支付固定（标准预配吞吐量）或可变（自动缩放）费用的用户进行了优化。 实际 RU 费用取决于所选的模型：预配吞吐量（标准或自动缩放）或无服务器。
vCore 服务变体创建利用预设 CPU、内存和存储资源的专用实例，这些资源可动态缩放以满足你的需求。 此服务针对更愿意基于计算（CPU、内存和节点数）和存储支付一致的固定费用的用户进行了优化。