Comparison Item | Yearly/Monthly Subscription | Pay-as-You-Go |
Billing method | Prepaid: Pay the full fee for the selected duration (such as month and year) in one go. Purchase Period: Purchase monthly or yearly. The minimum period is 1 month, and the maximum is 5 years. Product Pricing: Priced monthly, with greater discounts for longer purchase periods. For specific pricing, see Product Pricing. | Postpaid: Billed hourly. Pay after usage. Settlement cycle: Upon activation, one hour's fee will be frozen in your cloud account. At the top of every hour (UTC+8), the fee for the previous hour will be settled automatically. Product Pricing: Tiered pricing based on usage duration, with hourly rates decreasing tier by tier. For specific pricing, see Product Pricing. If the duration is greater than 0 days and less than or equal to 4 days, the first-tier pay-as-you-go pricing applies. If the duration is greater than 4 days and less than or equal to 15 days, the second-tier pay-as-you-go pricing applies. If the duration is greater than 15 days, the third-tier pay-as-you-go pricing applies. Note: After instance scale-out, scale-in, or isolation, the pricing calculation restarts from Tier 1. The price of pay-as-you-go tier 3 is basically the same as that of yearly/monthly subscription. |
Key rules | Renewal: Upon expiration, instances can be renewed manually or automatically. For detailed renewal instructions, see Instance Renewal (Yearly/Monthly Subscription). Refund: You can unsubscribe from an instance at any time, and the remaining fees will be settled according to the refund policy. For the specific refund policy, see Instance Refund (Yearly/Monthly Subscription). Overdue Payments: If an instance expires without renewal and remains in arrears beyond the grace period and retention period, the instance will be released. For details on how to deal with overdue payments, see Overdue Payments. Whether conversion to pay-as-you-go is supported: No. | Terminate: You can terminate an instance at any time, and used fees are settled by the second. For specific instructions, see Refund/Terminate Instance (Recycle Bin Isolation). Payment overdue: When the account balance is insufficient, instances will be released after the grace/retention period is exceeded. For specific overdue handling mechanisms, see Payment Overdue Policy. Whether conversion to yearly/monthly subscription is supported: Yes. For detailed instructions, see Convert Pay-as-You-Go to Yearly/Monthly Subscription. |
Key strength | Lower unit prices, and more favorable long-term usage costs. | Highly flexible, with on-demand resource purchase and release to adapt to business fluctuations. |
Applicable Scenario | Production environments or core business that is stable and operates over the long term. | Business with significant traffic fluctuation and temporary needs (such as development and testing and promotional campaigns). |
Billing Items | Description |
Billable Item | Billing is based on instance specifications (CPU and memory configurations) and storage capacity, encompassing the consolidated costs of the following core resources. Core component: Mongod node's CPU and memory resources, which handle core features such as data storage, query processing, and transaction execution. Extension component (for sharded clusters only): Mongos routing node's CPU and memory resources, which handle cross-shard request scheduling, load balancing, and query optimization. Storage resources refer to the dedicated disk capacity used by Mongod nodes for persistent storage of documents, indexes, and metadata. Due to variations in infrastructure costs (such as the power supply, network bandwidth, and data center Ops) and local market policies across different regions, the storage unit price is independently set for each region. For price details, see |
Pricing Description | Tiered pricing: Node prices are reduced as node capacity increases. For specific pricing, see Product Pricing. Architectural differences: Replica sets and sharded clusters adopt different specification tiers and pricing standards due to variations in performance, features, and complexity. Replica sets are divided into 4 specification tiers: less than 128 GB, equal to 128 GB, equal to 240 GB, and equal to 512 GB. Sharded clusters are divided into 2 specification tiers: less than 512 GB and equal to 512 GB. Different regions implement independent pricing tables based on infrastructure cost variations. Free tier (Mongos nodes): Mongos routing nodes provide a free tier (3 nodes for single-AZ, 6 nodes for multi-AZ), with additional nodes charged separately. |
Calculation Formula | For purchasing replica set instances or sharded cluster instances, see Billing Formula for fee calculation. |
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan