All Products
Search
Document Center

ApsaraMQ for RabbitMQ:Instance editions

Last Updated:Oct 15, 2024

This topic describes the instance editions provided by ApsaraMQ for RabbitMQ.

Description

Table 1. Instance editions

Category

Item

Serverless Edition

Professional Edition

Enterprise Edition

Enterprise Platinum Edition

Billing method

Pay-as-you-go.

You do not need to reserve resources in advance. If your usage does not exceed the specification limits, you are charged based on your actual usage.

For more information, see Billing of Serverless Edition instances.

Subscription.

The elastic transaction per second (TPS) feature is supported. After you enable this feature for an instance, the peak messaging TPS of the instance can be increased within a specific range.

For more information, see Billing of subscription instances.

High availability and reliability

Architecture

Shared instances with logical isolation.

Shared instances with logical isolation.

Shared instances with logical isolation.

Dedicated instances, each of which is deployed in a dedicated physical cluster.

Service availability

High availability with multiple-zone deployment

High availability with multiple-zone deployment

High availability with multiple-zone deployment

High availability with multiple-zone deployment

Data reliability

Three replicas for data persistence

Three replicas for data persistence

Three replicas for data persistence

Three replicas for data persistence

SLA

99.95%

99.95%

99.95%

99.99%

Features

Data observability, monitoring, and alerting

Managed Service for Prometheus and Managed Service for Grafana are used to support the dashboard feature. This feature allows you to view the data charts of various fine-grained metrics.

For more information, see Dashboard.

Data can be viewed in the ApsaraMQ for RabbitMQ console in real time.

For more information, see Monitoring and alerting.

Managed Service for Prometheus and Managed Service for Grafana are used to support the dashboard feature. This feature allows you to view the data charts of various fine-grained metrics.

For more information, see Dashboard.

Managed Service for Prometheus and Managed Service for Grafana are used to support the dashboard feature. This feature allows you to view the data charts of various fine-grained metrics.

For more information, see Dashboard.

Global message routing

Supported.

Not supported.

Supported.

Supported.

Transmission encryption

Transport Layer Security (TLS) V1.2 encryption

Supported.

Not supported.

Supported.

Supported.

Storage encryption

Not supported.

Not supported.

Not supported.

Supported.

Limits

Limits on clusters

A larger message size is supported.

Limits are imposed.

A larger message size is supported.

Few limits are imposed.

Limits on API operation calls

Limits are imposed.

Limits are imposed.

Limits are imposed.

No limits are imposed.

Limits on instance editions

Limits on clusters

Item

Serverless Edition

Professional Edition

Enterprise Edition

Enterprise Platinum Edition

Elastic TPS

Maximum value: 50000.

Half of the peak messaging TPS in the computing specification.

Equal to the peak messaging TPS in the computing specification. Maximum value: 50000.

Equal to the peak messaging TPS in the computing specification. Maximum value: 50000.

vhosts per instance

Maximum value: 200.

Valid values: number of queues to 200.

Maximum value: 200.

Maximum value: 4096.

Connections per instance

Maximum value: 10000.

Four times the number of queues.

Valid values: 1000 to 5000.

Purchase a connection quota based on the instance specification.

A free quota of at least 2,000 connections is provided for an instance. The maximum number of connections per instance is 10,000.

Purchase a connection quota based on the instance specification.

A free quota of 50,000 connections is provided for an instance. The maximum number of connections per instance is 100,000.

Exchanges per vhost

Equal to the number of queues.

Equal to the number of queues.

Equal to the number of queues.

None.

Bindings per vhost

10 times the number of queues.

Valid values: 4096 to 20000.

10 times the number of queues.

Valid values: 4096 to 20000.

10 times the number of queues.

Valid values: 4096 to 20000.

None.

Queues per instance

Maximum value: 6000.

Maximum value: 6000.

Maximum value: 6000.

Maximum value: 80000.

Queues bound to an exchange

Maximum value: 256.

Maximum value: 256.

Maximum value: 256.

Maximum value: 256.

If you want to increase the quota, contact Alibaba Cloud technical support.

Consumers per queue

Four times the number of queues.

Valid values: 800 to 5000.

Four times the number of queues.

Valid values: 50 to 5000.

Four times the number of queues.

Valid values: 800 to 5000.

None.

Channels per connection

Valid values: number of queues to 2048.

  • If the number of queues is less than 2,048, the maximum number of channels per connection is equal to the number of queues.

  • If the number of queues is greater than or equal to 2,048, the number of channels per connection is 2,048.

Valid values: 64 and number of queues.

  • If the number of queues is less than or equal to 64, the number of channels per connection is 64.

  • If the number of queues is greater than 64, the number of channels per connection is equal to the number of queues.

Valid values: Number of queues to 2048.

  • If the number of queues is less than 2,048, the maximum number of channels per connection is equal to the number of queues.

  • If the number of queues is greater than or equal to 2,048, the number of channels per connection is 2,048.

Maximum value: 3000.

Message size

Maximum value: 1 MB.

Maximum value: 64 KB.

Maximum value: 1 MB.

  • If a message is smaller than 64 KB in size, one API call is counted to process the message data.

  • If a message is larger than 64 KB in size, one API call is counted to process each 4 KB of the excess message data.

Maximum value: 1 MB.

Delay period for delayed messages

Maximum value: 7 days.

Maximum value: 24 hours.

Maximum value: 7 days.

Maximum value: 7 days.

Retention period for messages

Maximum value: 3 days.

Maximum value: 3 days.

Maximum value: 3 days.

Maximum value: 3 days.

Number of times that a message can be requeued

Maximum value: 16.

Maximum value: 16.

Maximum value: 16.

Maximum value: 64

Consumption timeout period

Maximum value: 15 minutes.

Maximum value: 10 minutes.

Maximum value: 15 minutes.

Maximum value: 60 minutes.

Limits on API calls

Item

Operation

Serverless Edition

Professional Edition

Enterprise Edition

Enterprise Platinum Edition

Synchronous message receiving on an instance

basicGet

500 TPS

500 TPS

500 TPS

None.

Queue clearance on an instance

purgeQueue

500 TPS

500 TPS

500 TPS

None.

Exchange creation on an instance

exchangeDeclare

500 TPS

500 TPS

500 TPS

None.

Exchange deletion on an instance

exchangeDelete

500 TPS

500 TPS

500 TPS

None.

Queue creation on an instance

queueDeclare

500 TPS

500 TPS

500 TPS

None.

Queue deletion on an instance

queueDelete

500 TPS

500 TPS

500 TPS

None.

Binding creation on an instance

queueBind

500 TPS

500 TPS

500 TPS

None.

Binding deletion on an instance

queueUnbind

500 TPS

500 TPS

500 TPS

None.

Message restoration on an instance

basicRecover

500 TPS

500 TPS

500 TPS

None.

Message requeuing on an instance

  • basicReject(requeue=true)

  • basicNack(requeue=true)

20 TPS

20 TPS

20 TPS

None.