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.
- 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 own billing rules. Message Queue for MQTT can interact only with Message Queue for Apache RocketMQ, for which you are charged for topic resource usage and API calls. For more information, see Message Queue for Apache RocketMQ 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 topic resource usage and API calls for Message Queue for Apache RocketMQ. Therefore, billing details about Message Queue for Apache RocketMQ are listed in the Product Cost Summary section.
Instance types and billing methodsThe following table describes the instance types and billing methods that are provided by Message Queue for Apache RocketMQ. For more information about the feature differences between these instance types, see Instance types.
|Instance type||Billing method||Description|
||Subscription||A billing method that allows you to use instance types 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 requires long-term running.|
|Pay-as-you-go instances||Pay-as-you-go||A billing method that allows you to use instance types before you pay for them. You can use this billing method if your business traffic demonstrates clear peaks and valleys or you only want to perform temporary testing. This helps prevent resource wastes.|
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 of the client API and the cloud API. In billing, the number of messages that correspond to a transmission quality level in the specified protocol is 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, 1 is multiplied by the corresponding calculation ratio.
The following table describes the calculation ratios in Message Queue for MQTT, which correspond to different transmission quality levels.
|Transmission quality level||Calculation ratio|
QoSparameter is set to 2 and the
cleanSessionparameter is set to false. However, if you set this transmission quality level, the calculation ratio is 5.
For more information about the QoS and cleanSession parameters, see Terms.
SubscriptionSubscriptionChange the billing method of an instance from subscription to pay-as-you-goRenew an instance and upgrade or downgrade the configuration of an instanceOverdue paymentsRefund rules and instructions
ReferencesInstance typesView bills