ApsaraMQ for RocketMQ provides Enterprise Platinum Edition instances and Standard Edition instances. You can refer to this topic to select an instance edition that meets your business requirements.
The following table describes the differences between Enterprise Platinum Edition instances and Standard Edition instances.
Item | Enterprise Platinum Edition instance | Standard Edition instance |
Billing method | Subscription | Pay-as-you-go |
Instance type | Dedicated instances, each of which is assigned a dedicated physical node. | Shared instances that are virtually isolated from each other. |
Availability | 99.99%. The cumulative downtime per month is no longer than 4.3 minutes. | 99.95%. The cumulative downtime per month is no longer than 21.5 minutes. |
Expert service |
| Not supported |
Message retention period | 3 days If the storage capacity that you purchased for your instance is insufficient, ApsaraMQ for RocketMQ automatically deletes the earliest stored messages. In this case, the messages may be retained for less than 3 days. Note If you want to specify a longer message retention period, contact ApsaraMQ for RocketMQ technical support. | 3 days |
Attribute-based SQL filtering | SQL expressions can be used to filter message attributes. This improves the efficiency of message subscription and processing. For more information about attribute-based SQL filtering, see Message filtering. | Not supported |
Transmission encryption | Encryption based on the Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocol is supported. SSL- or TLS-based encryption can be used only on clients that use the TCP client SDK for Java V2.x.x. For information about the TCP client SDK for Java, see Release notes. | To use SSL- or TLS-based encryption, submit a ticket. SSL- or TLS-based encryption must be used on clients that use the TCP client SDK for Java 2.x.x. For information about the TCP client SDK for Java, see Release notes. |
Message subscription in pull mode by using the SDK for Java | Supported For information about how to use the SDK for Java to subscribe to messages in pull mode, see Subscribe to messages. | Not supported |
Message trace | Supported For information about message traces, see Query message traces. | Supported |
Disaster recovery and high availability (HA) Note The zones in which an instance is deployed are determined by the resources on the ApsaraMQ for RocketMQ broker. You cannot specify custom values for zones. |
|
|