Billing

DMS for RabbitMQ supports pay-per-use.

Billing Items

DMS for RabbitMQ is billed based on RabbitMQ instance specifications and storage space.

**Table 1** Billing of DMS for RabbitMQ
Billing Item	Description
Instance	RabbitMQ instances are billed based on the specifications described in Table 2. RabbitMQ instances can be billed on a pay-per-use (hourly) basis.
Storage	RabbitMQ instances are also billed based on the storage space. For each type of instance specification, you can choose the high I/O or ultra-high I/O disk type to meet your service requirements. You can specify the number of replicas when creating a topic. For example, if the required disk size to store the message data is 100 GB and there are three replicas, the disk capacity should be at least: 100 GB x 3 = 300 GB. Storage space can be specified with increments of 100 GB. For details about the storage space range, see Table 2. Storage space can be billed on a pay-per-use (hourly) basis.

**Table 2** Specifications of RabbitMQ instances
Flavor	Brokers	Storage Space	Reference TPS	Maximum Consumers per Broker	Recommended Queues per Broker	Maximum Connections per Broker
rabbitmq.2u4g.single	1	100 GB–30,000 GB	10,000	20,000	200	3000
rabbitmq.4u8g.single	1	100 GB–30,000 GB	20,000	30,000	400	4500
rabbitmq.8u16g.single	1	100 GB–30,000 GB	35,000	50,000	800	7500
rabbitmq.16u32g.single	1	100 GB–30,000 GB	45,000	80,000	1600	12,000
rabbitmq.2u4g.cluster	3/5/7	3/5/7 x 100 GB–30,000 GB	30,000–70,000	20,000	200	3000
rabbitmq.4u8g.cluster	3/5/7	3/5/7 x 100 GB–30,000 GB	45,000–80,000	30,000	400	4500
rabbitmq.8u16g.cluster	3/5/7	3/5/7 x 100 GB–30,000 GB	85,000–120,000	50,000	800	7500
rabbitmq.12u24g.cluster	3/5/7	3/5/7 x 100 GB–30,000 GB	100,000–150,000	60,000	1200	10,000
rabbitmq.16u32g.cluster	3/5/7	3/5/7 x 100 GB–30,000 GB	130,000–180,000	80,000	1600	12,000

Mapping Between Old and New Flavors

Table 3 compares the old and new RabbitMQ instance flavors.

**Table 3** Mapping between old and new RabbitMQ instance flavors
Old Flavor	TPS (Old)	New Flavor	TPS (New)
2 vCPUs \| 4 GB x 1	10,000	rabbitmq.2u4g.single x 1	10,000
4 vCPUs \| 8 GB x 1	20,000	rabbitmq.4u8g.single x 1	20,000
8 vCPUs \| 16 GB x 1	35,000	rabbitmq.8u16g.single x 1	35,000
16 vCPUs \| 32 GB x 1	45,000	rabbitmq.16u32g.single x 1	45,000
4 vCPUs \| 8 GB x 3	45,000	rabbitmq.4u8g.cluster x 3	45,000
4 vCPUs \| 8 GB x 5	70,000	rabbitmq.4u8g.cluster x 5	70,000
4 vCPUs \| 8 GB x 7	80,000	rabbitmq.4u8g.cluster x 7	80,000
8 vCPUs \| 16 GB x 3	85,000	rabbitmq.8u16g.cluster x 3	85,000
8 vCPUs \| 16 GB x 5	110,000	rabbitmq.8u16g.cluster x 5	110,000
8 vCPUs \| 16 GB x 7	120,000	rabbitmq.8u16g.cluster x 7	120,000
16 vCPUs \| 32 GB x 3	130,000	rabbitmq.16u32g.cluster x 3	130,000
16 vCPUs \| 32 GB x 5	160,000	rabbitmq.16u32g.cluster x 5	160,000
16 vCPUs \| 32 GB x 7	180,000	rabbitmq.16u32g.cluster x 7	180,000

Assume that your service has 10,000 TPS and you need to reserve 30% of the traffic to accommodate traffic hikes, you can use the rabbitmq.4u8g.single x 1 flavor. If your service requires high availability, use the rabbitmq.4u8g.cluster x 3 flavor.

Billing Modes

Pay-per-use (hourly): This billing mode is flexible, enabling you to start and stop services anytime. You pay only for the actual usage duration. The minimum time unit is one hour. Less than an hour is recorded as an hour.