...
The other component is the cost of messages (incoming + outgoing). This means, if there is 1 publisher and 2 subscribers to one topic, 1 published message (incoming) will be delivered to 2 subscribers (outgoing), which means, there are 3 (1 incoming and 2 outgoing) messages to count:
...
Let's use the following scenario as an example.
1 IoT device connecting to HiveMQ Cloud 24/7 subscribing to 4 topics and publishing to 9 topics at the rate of 1 message per minute.
1 backend service connecting to HiveMQ Cloud 24/7 subscribing to topics in 2 wildcard patterns and publishing messages average of 500 messages a day.
1 web service connecting to HiveMQ Cloud to publish message an average of 500 messages a daydaily.
Messages from IoT will generally be around 1.04 kilobytes, and others will be around 8 bytes per message.
...
A change in message cadence might impact this number slightly.
A normalized message – for billing purposes, only PUBLISHED messages are counted. To to best balance billing between customers we ‘normalize’ messages to a value of 5KB. For example, if you send an 8KB message, it will be counted as two normalized messages. The message’s topic, headers, and payload (and if using MQTT5, user properties) are all combined in this sizing calculation.
...