This topic describes the billing methods and billable items of Message Queue for MQTT. You can select an instance type and a billing method based on your business requirements.
Related topicsInstance editionsSubscriptionRenew an instance and upgrade or downgrade the configuration of an instanceView billsOverdue paymentsRefund rules and instructions
- If you use Message Queue for MQTT V3.x.x to exchange data with other Alibaba Cloud services based on the specified rules, you are charged for these services based on their billing rules. Message Queue for MQTT can interact only with Message Queue for Apache RocketMQ, for which you are charged for the topic usage and API calls. For more information about the billing of Message Queue for Apache RocketMQ, see Billing overview.
- Message Queue for MQTT V2.x.x uses Message Queue for Apache RocketMQ for storage. When you use Message Queue for MQTT, you are also charged for the topic usage and API calls in Message Queue for Apache RocketMQ. You can view the billing details about Message Queue for Apache RocketMQ in the Product Cost Summary section.
Instance types and billing methodsMessage Queue for Apache RocketMQ The following table describes the instance types and billing methods that are provided by Message Queue for MQTT. For more information about the differences between the features of these instance types, see Instance editions.
|Instance type||Billing method||Description|
||Subscription instances||A billing method that allows you to use instances only after you pay for them. The subscription billing method allows you to reserve resources in advance and helps you minimize costs with high discounts. You can use this billing method if your system has a large amount of business traffic and you require the service for long-term usage.|
|Pay-as-you-go instance (end of sale)||Pay-as-you-go instances (end of sale)|
When you transmit messages by using the Message Queuing Telemetry Transport (MQTT) protocol, the settings of the QoS and cleanSession parameters affect the actual charges. You are charged for messages, including calls to the client API and the cloud API. In billing, the system calculates the number of messages as the product of the number of messages that correspond to a transmission quality level in the specified protocol multiplied by the calculation ratio that corresponds to this level. For example, if the number of messages that correspond to a transmission quality level is 1, the system calculates the number of messages as the product of 1 multiplied by the corresponding calculation ratio.
The following table describes the calculation ratios that correspond to different transmission quality levels in Message Queue for MQTT.
|Transmission quality level||Calculation ratio|
QoSparameter is set to 2 and the
cleanSessionparameter is set to false. If you specify this transmission quality level, the calculation ratio is 5.
For more information about the QoS and cleanSession parameters, see Terms.