This topic describes the specifications and pricing of ApsaraDB for POLARDB, including billing methods, billable items, storage space prices, data backup prices, and compute node prices.
Billing methods
You can use one of the following two billing methods to purchase ApsaraDB for POLARDB clusters.
- Subscription (prepaid billing)
Using a subscription billing method, you pay in advance for the compute cluster (for example, a primary node and a read-only node) that you create. Despite the subscription billing method, certain fees are incurred on a pay-as-you-go basis. For example, you are billed for the storage space you use by hour and the charge is deducted from your account balance on an hourly basis.
- Pay-as-you-go (postpaid billing)
Using a pay-as-you-go billing method, you pay for the resources after you use them. Regardless of the compute clusters or storage space, you are billed by hour and the charge is deducted from your account balance on an hourly basis.
Billable items
| Billing item | Billing method |
|---|---|
| Compute cluster (a primary node and one or more read-only nodes) | Subscription or pay-as-you-go. |
| Storage space | Pay-as-you-go |
| Data backup | Free of charge |
Storage space prices
If you select pay-as-you-go billling, storage space is charged as follows:
- The price for regions in mainland China: USD 0.00077/GB/hour
- The price for China (Hong Kong) and other regions outside mainland China: USD 0.00085/GB/hour
Data backup prices
Compute node prices
All nodes in ApsaraDB for POLARDB clusters are hosted on dedicated resources. The CPU, memory, storage, and input/output (I/O) resources assigned to a node are reserved for this node, instead of being shared with other nodes. This improves the stability and reliability of the node. The following table lists all types of nodes that are available.
| Node type | CPU and memory | Maximum storage space | Maximum number of connections | Internal network bandwidth | Maximum number of input/output operations per second (IOPS) | I/O bandwidth |
|---|---|---|---|---|---|---|
| polar.mysql.x2.medium |
2-core 4 GB |
5 TB | 1,200 | 1 Gbit/s | 8,000 | 1 Gbit/s |
| polar.mysql.x4.large |
4-core 16 GB |
10 TB | 5,000 | 10 Gbit/s | 32,000 | 4 Gbit/s |
| polar.mysql.x4.xlarge |
8-core 32 GB |
10 TB | 10,000 | 10 Gbit/s | 64,000 | 8 Gbit/s |
| polar.mysql.x8.xlarge |
8-core 64 GB |
30 TB | 10,000 | 10 Gbit/s | 72,000 | 10 Gbit/s |
| polar.mysql.x8.2xlarge |
16-core 128 GB |
50 TB | 20,000 | 10 Gbit/s | 128,000 | 16 Gbit/s |
| polar.mysql.x8.4xlarge |
32-core 256 GB |
50 TB | 64,000 | 10 Gbit/s | 192,000 | 24 Gbit/s |
| polar.mysql.x8.12xlarge |
88-core 710 GB |
50 TB | 64,000 | 25 Gbit/s | 256,000 | 32 Gbit/s |
| Node type | Mainland China | China (Hong Kong) | US (Silicon Valley) | Singapore | Indonesia (Jakarta) |
|---|---|---|---|---|---|
| polar.mysql.x2.medium |
USD 44/month USD 0.091/hour |
USD 76/month USD 0.117/hour |
USD 62/month USD 0.130/hour |
USD 76/month USD 0.16/hour |
USD 74/month USD 0.15/hour |
| polar.mysql.x4.large |
USD 155/month USD 0.323/hour |
USD 295/month USD 0.532/hour |
USD 240/month USD 0.500/hour |
USD 295/month USD 0.61/hour |
USD 271/month USD 0.57/hour |
| polar.mysql.x4.xlarge |
USD 310/month USD 0.646/hour |
USD 589/month USD 1.063/hour |
USD 480/month USD 1.000/hour |
USD 589/month USD 1.23/hour |
USD 542/month USD 1.13/hour |
| polar.mysql.x8.xlarge |
USD 496/month USD 1.033/hour |
USD 743/month USD 1.342/hour |
USD 620/month USD 1.290/hour |
USD 743/month USD 1.55/hour |
USD 689/month USD 1.44/hour |
| polar.mysql.x8.2xlarge |
USD 991/month USD 2.064/hour |
USD 1,486/month USD 2.684/hour |
USD 1,239/month USD 2.580/hour |
USD 1,486/month USD 3.10/hour |
USD 1,378/month USD 2.87/hour |
| polar.mysql.x8.4xlarge |
USD 1,982/month USD 4.128/hour |
USD 2,972/month USD 5.367/hour |
USD 2,477/month USD 5.160/hour |
USD 2,972/month USD 6.19/hour |
USD 2,756/month USD 5.74/hour |
| polar.mysql.x8.12xlarge |
USD 5,449/month USD 11.351/hour |
USD 8,173/month USD 14.756/hour |
USD 6,811/month USD 14.190/hour |
USD 8,173/month USD 17.03/hour |
USD 7,577/month USD 15.78/hour |
- Each price listed in the tables is for a single node. An ApsaraDB for POLARDB cluster consists of a primary node and a read-only node by default.
- You can select a node type for the primary node when you create a cluster. The same type is automatically applied to read-only nodes.
- The maximum number of IOPS is a theoretically calculated value.
- The maximum number of connections for a cluster depends on the specifications of nodes, and does not change with the number of nodes.
- If you need a higher computing capacity and larger storage space (for example, 100 TB), open a ticket.
FAQ
- What is the price if I want to add a read-only node?
For an ApsaraDB for POLARDB cluster, a read-only node has the same price as the primary node. For more information, see node types and prices.
- Will the maximum storage space be doubled if I add a read-only node?
No, ApsaraDB for POLARDB adopts a compute-storage separation architecture. Read-only nodes are used for computing, and do not change the maximum storage space of the cluster.
Based on a serverless architecture, you do not need to specify the storage space when creating a cluster. The cluster automatically scales out as the data size increases. You are only billed for the storage space you have used. The maximum storage space varies with node types. If you want to extend the maximum storage space, upgrade the specifications of your cluster.