This topic describes the billable items and pricing of pay-as-you-go instances in ApsaraMQ for MQTT.
Precautions
ApsaraMQ for MQTT no longer supports the pay-as-you-go billing method. You can continue to use existing pay-as-you-go instances.
Billable items
The following table describes the billable items of pay-as-you-go instances in ApsaraMQ for MQTT.
| Billable item | Definition | Description | Example |
|---|---|---|---|
| Number of concurrent connections | The number of TCP connections to a single instance at a point in time. The number of concurrent connections is a transient value. The value is updated every minute. | The billing cycle is one day. The system counts the maximum number of concurrent connections within the 24 hours that start from 00:00 on the previous day in each daily bill. | Assume that the number of concurrent connections to instance_a was 1,000 at 10:00 and 2,000 at 11:00 on August 8, 2017. The number did not reach 2,000 again on that day. In this case, the maximum number of concurrent connections to instance_a was 2,000 on August 8, 2017. As a result, the number based on which you are charged is 2,000. |
| Number of sent messages and received messages | The total number of messages that are sent and received by using protocols supported by ApsaraMQ for MQTT. |
| Assume that instance_a has 100 clients and cleanSession is set to true for each client. Each client sends one QoS 0 message, two QoS 1 messages, and three QoS 2 messages, and receives one QoS 0 message, one QoS 1 message, and one QoS 2 message. In this case, the total number of sent and received messages on instance_a is calculated by using the following formula: 100 × (1 + 2 × 2 + 3 × 5) + 100 × (1 + 1 × 2 + 1 × 5) = 2,800. The number based on which you are charged is 2,800. |
| Number of subscriptions | The number of subscription rules that you register with the Message Queue for MQTT broker. | The billing cycle is one day. The system counts the maximum number of subscriptions within the 24 hours that start from 00:00 on the previous day in each daily bill. | Assume that the number of subscriptions in instance_a was 1,000 at 10:00 and 500 at 11:00 on August 8, 2017. The number did not reach 1,000 again on that day. In this case, the maximum number of subscriptions in instance_a was 1,000 on August 8, 2017. As a result, the number based on which you are charged is 1,000. |
Pricing
The following table describes the pricing details for concurrent connections to pay-as-you-go instances in ApsaraMQ for MQTT.
| Number of concurrent connections | Price (USD) |
|---|---|
| [1,100] | 0.07 |
| > 100 | Number of concurrent connections × 0.0007 |
The following table describes the pricing details for the sent and received messages on pay-as-you-go instances in ApsaraMQ for MQTT.
| Number of sent and received messages (million) | Price (USD) |
|---|---|
| > 0 | Number of sent and received messages × 0.91 |
The following table describes the pricing details for subscriptions in pay-as-you-go instances in ApsaraMQ for MQTT.
| Number of subscriptions | Price (USD) |
|---|---|
| [1,100] | 0.01 |
| > 100 | Number of subscriptions × 0.0001 |