Introduction Message Queue for MQTThelp you choose the appropriate instance types and billing modes as needed.
- Message Queue for MQTTSince V3.x.x release no longer begins Message Queue for Apache RocketMQis the storage. Single Message Queue for MQTTinstance can create up to 25 topics. The error message returned because the number of instances has been exceeded. submit a ticket processing, the future will charge for the excess resources.
- If you use Message Queue for MQTTin V3.x.x, you can use rules to interact with other Alibaba cloud products. The corresponding fees are subject to the billing instructions of the specific products. For the currently only supported Message Queue for Apache RocketMQ, a Topic resource occupation fee and API call fee are charged. For more information, see Message Queue for Apache RocketMQdetailed price overview.
Message Queue for MQTTThe instance types are as follows:
|Parameter||Platinum Edition||Basic Edition||pay-as-you-go|
|Instance type||Dedicated instance (physical isolation). You can use exclusive hardware resources to protect your instances. Each instance is deployed as a cluster independently. Such instances will not be affected by service peaks of other users, providing after-sales services and ensuring stability with a higher priority.||Shared instances (logical isolation). Where multiple instances share the same backend cluster, Message Queue for MQTTto ensure service availability in multi-tenant scenarios.||Shared instances (logical isolation). Where multiple instances share the same backend cluster, Message Queue for MQTTto ensure service availability in multi-tenant scenarios.|
|Billing methods||Cloud Firewall uses the subscription billing method. Subscription is billed based on the specification.||Pay-as-you-go Pay-as-you-go is billed based on the actual usage.|
|Service Support||Product consulting DingTalk Group||✓||✓||✓|
|Alibaba Cloud engineering single channel||✓||Cost||Cost|
|Exclusive Channel for Alibaba Cloud tickets||✓||Cost||Cost|
|System launch and promotion support service||✓||Cost||Cost|
|Exclusive Support DingTalk Group||✓||Cost||Cost|
|Dedicated Service manager support||✓||Cost||Cost|
|Exclusive technical expert support||✓
Provides direct technical support from the core R&D team.
|Point-to-point fault handling||✓
on-call for 24 hours × 7 days.
|Feature||Subscription relationship restriction for a single device (rule)||Theoretically unlimited
Custom subscription restrictions (rules) for a single device.
|Up to 30||Up to 30|
|MessageRetentionPeriod||Up to 7 days
Custom message retention time
|Up to 3 days||Up to 3 days|
|Device online /offline notification||✓||✓||✓|
|Third-party account authorization||✓||✓||✓|
Message Queue for MQTTThe following table describes the billing items for subscription instances.
|Maximum number of concurrent connections||The maximum number of client TCP connections on a single instance at any time. The number of concurrent online connections is a transient value and is updated every minute.||Make sure that the upper limit of the number of online connections is greater than or equal to the actual number of business connections, avoid business connections in the peak pulse is triggered Message Queue for MQTTservice throttling, causing some clients to fail to connect.||If you set instance_a to 1,000 simultaneous connections at 10:00 and 2,000 simultaneous connections at 10:01, then instance_a needs to exceed the maximum number of 2,000 connections (for example, 5,000) to ensure the normal operation of the service.|
|Maximum message TPS||Use per second Message Queue for MQTTthe maximum number of messages that can be sent uplink and received downlink.||
||instance_a has 100 clients, and cleanSession is set to true for each client. This method sends one QoS0 message, two QoS1 messages, and three QoS2 messages per second, and receives one QoS0 message, one QoS1 message, and one QoS2 message per second. If the message TPS of instance_a is 100 x(1+2 x 2+3 x 5)+100 x(1+1 x 2+1 x 5)= 2800 messages /second, instance_a needs to exceed the maximum message TPS of 2800 messages /second (3000 messages /second). To ensure normal service operation.|
|Maximum number of subscription relationships||The maximum number of subscription rules that you can register with the MQTT broker.||
||instance_a has two devices: client_1 and client_2. client_1 subscribes to TopicA/sub_1, TopicA/sub_2, and TopicB/sub_1. client_2 subscribes to TopicA/sub_1 and TopicB/sub_2. instance_a has three subscription relationships (3+2 = 5). Therefore, instance_a needs to contain more than five subscription relationships (1000, for example). To ensure normal service operation.|
Message Queue for MQTTThe following figure shows the billing method for the maximum number of connections for a subscription instance.
|Instance type||Maximum number of concurrent connections||Price (USD /month)|
|Basic Edition instance||100||3|
|Enterprise Platinum Edition instance||100,000||3852|
Message Queue for MQTTThe following figure shows the maximum message delivery network (TPS) billing method for subscription instances.
|Instance type||Maximum message transactions per second||Price (USD /month)|
|Basic Edition instance||100||29|
|Enterprise Platinum Edition instance||20,000||5211|
Message Queue for MQTTThe following figure shows the billing method for the maximum number of subscriptions for a subscription instance.
|Instance type||Maximum number of subscription relationships||Price (USD /month)|
|Basic Edition instance||1 thousand||12|
|Enterprise Platinum Edition instance||100,000||1586|
Message Queue for MQTTThe following table describes the billing items for pay-as-you-go instances.
|Concurrent online connections||The number of client TCP connections on a single instance at any time. The number of concurrent online connections is a transient value and is updated every minute.||The billing cycle is one day, that is, the maximum number of concurrent online connections in the 24 hours from 00:00 in the previous day is counted in the daily bill.||The number of concurrent online connections at instance_a 2017-08-08 10:00 was 1000,2017-08-08: 00 was 2000, and did not reach 2000 after 2017-08-08. The maximum number of concurrent online connections of instance_a on 2017-08-08 was 2000, and the billing value was 2000.|
|Sent and received messages||Use Message Queue for MQTTthe total number of messages that are sent uplink and received downlink.||
||instance_a has 100 clients, and cleanSession is set to true for each client, which sends one QoS0 message, two QoS1 messages, three QoS2 messages, one QoS0 message, one QoS1 message, and one QoS2 message. The number of sent and received messages of instance_a is 100 x(1+2 x 2+3 x 5)+100 x(1+1 x 2+1 x 5)=2,800, and the billing value is 2,800.|
|Subscription relationships||The number of subscription relationships refers to the number of subscription rules that a user has registered with the MQTT broker.||The billing cycle is one day, that is, the maximum number of subscription relationships in the 24 hours from 00:00 of the previous day is counted in the daily bill.||The number of subscription relationships for instance_a 2017-08-08 10:00 is 1,000, 500 are deleted at 11:00 on 2017-08-08, and the number is not reached at all at the following time. The maximum number of subscription relationships for instance_a on 2017-08-08 is 1,000, and the billing value is 1,000.|
Message Queue for MQTTThe following table lists the billing rules for concurrent online connections of a pay-as-you-go instance.
|Number of concurrent online connections (count)||Price (USD)|
|> 100||Number of concurrent online connections × 0.0007|
Message Queue for MQTTThe billing rules for the number of sent and received messages of a pay-as-you-go instance are as follows:
|Sent and received messages (millions of messages)||Price (USD)|
|> 0||Sent and received messages × 0.91|
Message Queue for MQTTThe following table describes the billing rules for the subscription of pay-as-you-go instances.
|Subscription relationships||Price (USD)|
|> 100||Number of subscription relationships × 0.0001|
Message Queue for MQTTThe message pricing ratio is as follows:
|Transmission quality level||Calculation ratio|
|QoS = 0 and cleanSession = true in MQTT||1|
|QoS = 0 and cleanSession = false in MQTT||1|
|QoS = 1 and cleanSession = true in MQTT||2|
|QoS = 1 and cleanSession = false in MQTT||5|
|QoS=2 and cleanSession=true in MQTT||5|