プライバシーポリシー
データプライバシーとセキュリティ契約
Edition Type | Basic Edition (Not Available for Sale) | Pro Edition | Platinum Edition |
TPS Specification | Two specification options are available: 2000 and 5000. TPS units are converted according to Billing Rules. Excess messages sent or received will be rejected. | Multiple specification options within 2000–50000. TPS units are converted according to Billing Rules. Excess messages sent or received will be rejected. | Multiple specification options ranging from 50000 TPS to 5 million TPS, with up to 10 million connections. TPS units are converted according to Billing Rules. Excess messages sent or received will be rejected. If you require higher specifications for the Platinum Edition, please submit a ticket to contact us. |
Resource Isolation | All components are deployed in high availability mode. The computing layer is physically dedicated, while the storage layer and other Basic Edition clusters share physical resources and are logically isolated. | All components are deployed in high availability mode. The computing layer is physically dedicated, while the storage layer and other Pro Edition clusters share physical resources and are logically isolated. | All components are physically dedicated and deployed in high availability mode. |
Server-Side ReceiveMaximum Setting | ReceiveMaximum = 16. In the MQTT 5.0 protocol, the server-side Receive Maximum setting indicates the maximum number of QoS 1 and QoS 2 PUBLISH packets that the server can process concurrently. QoS 0 packets are not limited. If the limit is exceeded, consumption requests will be rejected. | ReceiveMaximum = 1024. In the MQTT 5.0 protocol, the server-side Receive Maximum setting indicates the maximum number of QoS 1 and QoS 2 PUBLISH packets that the server can process concurrently. QoS 0 packets are not limited. If the limit is exceeded, consumption requests will be rejected. | |
Maximum Online Client Connections | The default ratio with TPS is 1:1 and cannot be adjusted. Client connections will be rejected if the limit is exceeded. | Can be freely adjusted within a range of 1 to 10 times the TPS. Client connections will be rejected if the limit is exceeded. | |
Authentication Method | Supports default password authentication and SSL certificate authentication only. The "one-device-one-certificate" feature is not supported. | In addition to passwords and SSL certificates, third-party authentication can be integrated. Currently, only JWT authentication is supported. More custom external authentication sources will be added later. Supports the "one-device-one-certificate" feature (manual or automatic registration of device certificates and CA certificates). | |
Data Plane Authorization Management | Supports fine-grained authorization policies (client, IP, topic, and so on), with up to 10 policies configured concurrently. | Supports fine-grained authorization policies (client, IP, topic, and so on), with up to 20–50 policies configured concurrently. | |
Sending Messages via HTTP(S) | Not supported. | Supported. | |
P2P Messaging Mode | Not supported. | Supported. With the consumer's client ID, messages can be sent directly to that client. | |
フィードバック