All Products
Search
Document Center

ApsaraMQ for MQTT:Instance editions

Last Updated:Sep 06, 2024

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

Table 1. Instance editions

Table 2. Instance editions

Item

Enterprise Platinum Edition

Basic Edition

Instance type

Dedicated instances. Instances of this type are physically isolated from each other. Each Platinum Edition instance owns exclusive underlying hardware resources and is deployed as a standalone cluster. This ensures that your business is not affected by the traffic peaks of other users. Compared with other editions of instances, this edition provides faster customer support and higher stability.

Shared instances. Instances of this type are logically isolated from each other. Multiple Basic Edition instances share underlying hardware resources and are deployed in the same backend cluster. ApsaraMQ for MQTT ensures service availability in multitenancy scenarios.

Billing method

Subscription. A yearly or monthly upfront payment is required based on the specifications that you select.

Scenario

  • Large business scale

  • Custom services required

  • High limit requirements on the messaging transactions per second (TPS), the number of connections, and the number of subscriptions

  • Small business scale

  • Moderate limit requirements on the messaging TPS, the number of connections, and the number of subscriptions

Technical support

DingTalk group for product consultation

Alibaba Cloud ticket system

System launches and promotional events

Exclusive DingTalk group

Dedicated service manager

Dedicated technical expert

Technical support is provided by the core R&D team.

Point-to-point (P2P) troubleshooting

Customer support are available on a 24/7 basis.

Feature

Upper limit of subscriptions or rules on a device

Theoretically, no upper limit is imposed.

You can specify a custom value for the upper limit of subscriptions or rules on a device.

Up to 30 subscriptions or rules are supported.

Message retention period

Messages can be retained for up to seven days.

You can specify a custom value for the message retention period.

Messages can be retained for up to three days.

Protocol

MQTT

You can specify a custom protocol.

MQTT

Client status notification

P2P messaging

Message trace

Ordered messages

Authorization of third-party accounts

WebSocket

Management API operation

Note
  • A check mark (√) indicates that the service or feature is supported, and a cross (✗) indicates that the service or feature is not supported. For product consultation, join the DingTalk group to contact us.

  • ApsaraMQ for MQTT no longer supports the pay-as-you-go billing method. You can continue using existing pay-as-you-go instances. For more information, see Pay-as-you-go instances (end of sale).