Enterprises are deploying Internet of Things (IoT) solutions to collect and manage data from devices and increase returns. However, enterprises are facing various challenges in building a powerful IoT system. Alibaba Cloud IoT Platform offers solutions to these challenges and has advantages over user-created MQTT clusters and MQTT servers.
Differences between IoT Platform and user-created MQTT clusters
The following table describes the differences between Alibaba Cloud IoT Platform and user-created MQTT clusters in terms of capability.
|Item||Alibaba Cloud IoT Platform||User-created MQTT cluster|
Multiple billing methods: pay-as-you-go and subscription.Supports automatic scaling to meet business growth.
|Subscription, which requires a one-time investment on IaaS.
Requires manual scaling to meet business growth.
Provides device SDKs to enable quick connections between devices and IoT Platform. IoT Platform supports connections to devices around the world. These devices include devices in heterogeneous networks, devices that run in various environments, and devices that run based on different protocols.
Supports stable connections to hundreds of millions of devices, and automatic scaling. IoT Platform processes device messages within 50 ms.
Requires infrastructure and support from embedded system developers and cloud developers. The development features heavy workload and low efficiency.
The architecture may have difficulties in maintaining stable connections to millions of devices. A large number of devices going online and offline may cause the platform to collapse.
|Concurrency||Processes millions of concurrent messages and supports horizontal scaling. The core message processing system uses a stateless architecture without failure dependency. If a message fails to be sent, the system retries the request.||The architecture may have difficulties in processing millions of concurrent messages. A large number of concurrent upstream and downstream messages have negative impacts on the system. The peak load shifting feature is not supported. In this case, the service is limited during peak hours.|
|Security||Supports three levels of Multi-Level Protection Scheme (MLPS) 2.0 to protect device
||Requires the development and deployment of security measures. Securing device data
is a challenge.
If an enterprise does not have security professionals or sufficient security awareness, the enterprise cannot eliminate security risks in a timely manner.
Adopts multi-data center deployment to eliminate failure dependency.Guarantees service availability of 99.9%. If the guaranteed service availability is not reached, claims will be settled based on the relevant standard. IoT Platform can detect a fault within 1 minute, locate a fault within 5 minutes, and troubleshoot a fault within 20 minutes.
|Requires manual troubleshooting. If the MQTT cluster does not respond during data
migration, you must locate and resolve the fault. Service may be interrupted during
the data migration. Therefore, service availability is not guaranteed.
Provides no quantitative service availability. Errors must be handled by the technical team and the O&M team. The timeliness of error handling cannot be guaranteed. Enterprises must bear the losses that are caused by the errors.
|Usability||Supports plug-and-play deployment, and provides a console, device SDKs, and IoT Platform
SDKs to simplify development and deployment.
Provides a one-stop device management platform that monitors devices in real time. IoT Platform is also integrated with multiple Alibaba Cloud services. IoT Platform allows you to build complex IoT applications with ease.
Supports Thing Specification Language (TSL) models. TSL models eliminate the need to define data syntax, and simplify data analysis and visualization.
Provides a comprehensive monitoring and alert platform. After you configure the alert settings, you can receive alerts in real time if a system or business exception occurs.Provides APIs and supports data transfer among devices, IoT Platform, and business servers.
|Requires server deployment to build a load-balanced distributed architecture, and
requires big investment into an IoT system that handles connection, computing, and
Provides no consoles. Enterprises must set up both the frontend and backend. The device connection management, lifecycle management, and remote O&M are complex to implement.
|Global access||Available in six regions, distributed in Asia, Europe, and North America. Your devices
can be connected to the nearest access point.
Provides the domain acceleration feature to reduce the latency in global communications.Complies with GDPR provisions to ensure data security.
|Requires high costs to deploy devices in other regions. High latency is required to access these devices. Security compliance must also be considered.|
|Synchronous server call||Supports synchronous RRPC responses.||Not supported.|
|Data parsing based on custom protocols||Supports data parsing based on custom protocols. The related scripts are hosted on the cloud.||Not supported. The data must be parsed by business servers.|
|Data forwarding||Supports data forwarding among various cloud services by using the rules engine after you complete configurations.||Not supported. Coding is required to implement the data forwarding feature.|
|Firmware updates||Supports multiple firmware update modes.|
|Logging||Supports the log query feature and large-scale log storage.|
|Real-time monitoring||Visualizes real-time metric data on charts, and supports threshold-based alerts and event alerts.|