This topic describes the specifications and pricing of ApsaraDB for POLARDB, including billing methods, billing items, storage space prices, SQL insight prices, data backup prices, and compute node prices.

Billing methods

You can use either of the following billing methods to purchase ApsaraDB for POLARDB clusters.

  • Subscription

    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

    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.

Billing items

The following table lists the billing items of an ApsaraDB for POLARDB cluster.
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 This feature is currently available for free.

Storage space prices

The storage space includes the space for data, system files, log files (online logs and archived logs), and temporary files.
Note After you purchase an ApsaraDB for POLARDB cluster, the system automatically creates the preceding files required for normal database operation. The files occupy certain storage space.

Pay-as-you-go

The storage space is based on a serverless architecture. Therefore, 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. You can view the storage space you have used on the Basic Information page in the console.
  • 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
Note The maximum storage space varies depending on the node specifications. If you want to extend the maximum storage space, upgrade the specifications of your cluster.

SQL Explorer prices

You are billed based on the storage space consumed by audit logs.

  • The price for regions in mainland China: USD 0.0013/GB/hour
  • The price for China (Hong Kong) and other regions outside mainland China: USD 0.0019/GB/hour
Note Only the pay-as-you-go billing method is supported.

Data backup prices

The storage occupied by ApsaraDB for POLARDB backup files is free of charge.

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 exclusive to this node and not shared with other nodes. This improves the stability and reliability of the node. The following table lists all types of nodes that are available.

Table 1. POLARDB for MySQL node types
Node type CPU and memory Maximum storage space Maximum number of connections Internal network bandwidth Maximum number of IOPS I/O bandwidth
polar.mysql.x4.medium

2 cores

8 GB

5 TB 1,200 1 Gbit/s 8,000 1 Gbit/s
polar.mysql.x4.large

4 cores

16 GB

10 TB 5,000 10 Gbit/s 32,000 4 Gbit/s
polar.mysql.x4.xlarge

8 cores

32 GB

10 TB 10,000 10 Gbit/s 64,000 8 Gbit/s
polar.mysql.x8.xlarge

8 cores

64 GB

30 TB 10,000 10 Gbit/s 72,000 10 Gbit/s
polar.mysql.x8.2xlarge

16 cores

128 GB

50 TB 20,000 10 Gbit/s 128,000 16 Gbit/s
polar.mysql.x8.4xlarge

32 cores

256 GB

50 TB 64,000 10 Gbit/s 192,000 24 Gbit/s
polar.mysql.x8.12xlarge

88 cores

710 GB

50 TB 64,000 25 Gbit/s 256,000 32 Gbit/s
Note An ApsaraDB for POLARDB cluster with a 2-core CPU and 4-GB memory provides the basic specifications required in tests, trials, and other scenarios with low loads. We recommend that you do not use this type of nodes in a high-load production environment. Instead, we recommend that you use an ApsaraDB for POLARDB cluster with an 8-core CPU and 32-GB memory or higher specifications.
Table 2. POLARDB for MySQL prices
Node type Mainland China China (Hong Kong) US (Silicon Valley) Singapore Indonesia (Jakarta) Malaysia (Kuala Lumpur) Germany (Frankfurt)
polar.mysql.x4.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

USD 76/month

USD 0.16/hour

USD 67/month

USD 0.14/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

USD 295/month

USD 0.61/hour

USD 264/month

USD 0.55/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

USD 589/month

USD 1.23/hour

USD 527/month

USD 1.10/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

USD 743/month

USD 1.55/hour

USD 651/month

USD 1.36/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

USD 1,486/month

USD 3.10/hour

USD 1,301/month

USD 2.71/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

USD 2,972/month

USD 6.19/hour

USD 2,601/month

USD 5.42/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

USD 8,173/month

USD 17.03/hour

USD 7,229/month

USD 15.06/hour

Table 3. POLARDB for PostgreSQL node types
Node type CPU and memory Maximum storage space Maximum number of connections Internal network bandwidth Maximum number of IOPS I/O bandwidth
polar.pg.x4.medium

2 cores

8 GB

5 TB 400 1 Gbit/s 16,000 1 Gbit/s
polar.pg.x4.large

4 cores

16 GB

10 TB 800 10 Gbit/s 64,000 4 Gbit/s
polar.pg.x4.xlarge

8 cores

32 GB

10 TB 1,600 10 Gbit/s 128,000 8 Gbit/s
polar.pg.x8.xlarge

8 cores

64 GB

30 TB 3,200 10 Gbit/s 160,000 10 Gbit/s
polar.pg.x8.2xlarge

16 cores

128 GB

50 TB 6,400 10 Gbit/s 256,000 16 Gbit/s
polar.pg.x8.4xlarge

32 cores

256 GB

50 TB 12,800 10 Gbit/s 384,000 24 Gbit/s
polar.pg.x8.12xlarge

88 cores

710 GB

100 TB 36,000 25 Gbit/s 512,000 32 Gbit/s
Table 4. POLARDB for PostgreSQL prices
Node type Mainland China China (Hong Kong) US (Silicon Valley)
polar.pg.x4.medium

USD 795.6/year

USD 78/month

USD 0.163/hour

USD 1,509.6/year

USD 148/month

USD 0.226/hour

USD 1,224/year

USD 120/month

USD 0.202/hour

polar.pg.x4.large

USD 1,581/year

USD 155/month

USD 0.324/hour

USD 3,009/year

USD 295/month

USD 0.533/hour

USD 2,448/year

USD 240/month

USD 0.434/hour

polar.pg.x4.xlarge

USD 3,162/year

USD 310/month

USD 0.646/hour

USD 6,007.8/year

USD 589/month

USD 1.064/hour

USD 4,896/year

USD 480/month

USD 0.867/hour

polar.pg.x8.xlarge

USD 5,059.2/year

USD 496/month

USD 1.033/hour

USD 7,578.6/year

USD 743/month

USD 1.342/hour

USD 6,324/year

USD 620/month

USD 1.12/hour

polar.pg.x8.2xlarge

USD 10,108.2/year

USD 991/month

USD 2.065/hour

USD 15,157.2/year

USD 1,486/month

USD 2.684/hour

USD 12,637.8/year

USD 1,239/month

USD 2.237/hour

polar.pg.x8.4xlarge

USD 20,216.4/year

USD 1,982/month

USD 4.128/hour

USD 30,314.4/year

USD 2,972/month

USD 5.367/hour

USD 25,265.4/year

USD 2,477/month

USD 4.472/hour

polar.pg.x8.12xlarge

USD 55,579.8/year

USD 5,449/month

USD 11.352/hour

USD 83,364.6/year

USD 8,173/month

USD 14.757/hour

USD 69,472.2/year

USD 6,811/month

USD 12.297/hour

Table 5. Node types of POLARDB compatible with Oracle
Node type CPU and memory Maximum storage space Maximum number of connections Internal network bandwidth Maximum number of IOPS I/O bandwidth
polar.o.x4.medium

2 cores

8 GB

5 TB 400 1 Gbit/s 16,000 1 Gbit/s
polar.o.x4.large

4 cores

16 GB

10 TB 800 10 Gbit/s 64,000 4 Gbit/s
polar.o.x4.xlarge

8 cores

32 GB

10 TB 1,600 10 Gbit/s 128,000 8 Gbit/s
polar.o.x8.xlarge

8 cores

64 GB

30 TB 3,200 10 Gbit/s 160,000 10 Gbit/s
polar.o.x8.2xlarge

16 cores

128 GB

50 TB 6,400 10 Gbit/s 256,000 16 Gbit/s
polar.o.x8.4xlarge

32 cores

256 GB

50 TB 12,800 10 Gbit/s 384,000 24 Gbit/s
polar.o.x8.12xlarge

88 cores

710 GB

100 TB 36,000 25 Gbit/s 512,000 32 Gbit/s
Table 6. Prices of POLARDB compatible with Oracle
Node type Mainland China
Monthly subscription Yearly subscription Pay-as-you-go
polar.o.x4.medium USD 161 USD 1,642.2 USD 0.336
polar.o.x4.large USD 322 USD 3,284.4 USD 0.672
polar.o.x4.xlarge USD 644 USD 6,568.8 USD 1.342
polar.o.x8.xlarge USD 830 USD 8,466 USD 1.729
polar.o.x8.2xlarge USD 1,660 USD 16,932 USD 3.458
polar.o.x8.4xlarge USD 3,319 USD 33,853.8 USD 6.914
polar.o.x8.12xlarge USD 9,126 USD 93,085.2 USD 19.013
Note
  • 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 will be 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), you can submit a ticket.

FAQ

  • Q: What is the price if I want to add a read-only node?

    A: For an ApsaraDB for POLARDB cluster, a read-only node has the same price as the primary node. For more information, see Compute node prices.

  • Q: Will the maximum storage space be doubled if I add a read-only node?

    A: 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.

    The storage space is based on a serverless architecture. Therefore, 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 according to node types. If you want to extend the maximum storage space, upgrade the specifications of your cluster.