For enterprises that are eager to carry out IoT business, one highlight of EMQX Cloud, a fully-managed cloud-native MQTT message service, is that it can extract, filter, split and convert the data of Internet of things in real-time through a high-performance built-in rule engine, thus simplifying the development of IoT applications and accelerate business delivery. An out-of-box data bridging feature based on rule engine can help users to implement connections with various cloud services, such as Kafka, MongoDB, AWS RDS, AWS DocumentDB and InfluxDB, etc. and forward the IoT data to various third-party databases, message queues and data systems as per requirements.
Rule engine is undoubtedly an edge tool of EMQX Cloud to help users implement flexible data processing and integration. To enable users to get started easily and exert the value of this killer feature in practical project applications, the EMQX Cloud team recently upgraded and optimized it.
The rule engine has been officially renamed Data Integration. Meanwhile, the revised and upgraded UI has made it easier for users to understand, operate and manage. Compared with the previous version, the new Data Integration helps users quickly know the creation of resources and rules step by step by navigation. The users only need to follow the procedure of “creating resources - creating rules - adding actions - test and runing” to complete the configuration of rules. The specific procedure is as follows:
- First, specify the data architecture of your own business and the data integration system that needs to be docked with EMQX Cloud in [Create Resources], namely, what kind of third-party database, message queue, or business system interface to forward the data to. This is to create the connection information of relevant integrated systems for use in next steps.
- In [Create Rule], use SQL statement to create a rule to match the data from the device based on your business requirements, namely, define [what data needs to be processed and integrated].
- Select the well-defined resource in [Add Action], that is, which service the data will be sent to, namely, "where will the data go after processing". At the same time, the format of message storage and integration is defined through the message content template, that is, [how data is processed].
After the three steps above, the users can complete the setting of processing and unloading the equipment data, and complete the data integration after further testing and operation.
The brand new revision of [Data Integration] will make the use logic of the rule engine more consistent with users' habits and provide convenience for users to create IoT platforms and applications to meet business requirements with EMQX Cloud.
Appendix: Data Integration Feature Guide
Get acquainted with the following concepts before using data integration features, and in the introduction overview of [Data Integration], you can operate by following the guidance.
Meanwhile, please also note the version of EMQX Cloud you are using:
- Resources only support public network access. Therefore, before creating resources, you need to ensure that the resources have public network access capability and open the security group. There is no need to create VPC peer connections.
- For resource types, only Webhook and MQTT bridging connection is opened.
- Before opening the NAT gateway, resources only support intranet access, so you need to configure VPC peer connection and open the security group before creating resources.
- After opening the NAT gateway, you can access through the public network.
Use EMQX Cloud data integration feature to collect simulated temperature and humidity data, and dumping it to MySQL as an example: https://docs.emqx.com/en/cloud/latest/rule_engine/rule_engine_save_mysql.html#mysql-configuration
Reference documents: https://docs.emqx.com/en/cloud/latest/rule_engine/introduction.html