Using rule engine configuration to monitor offline events can push the fault information to the application service and realize the ability of first-time fault detection in the access layer.
Use the rules engine to conditionally filter messages before passing them into the business system, significantly reducing the load on the business system.
In the intelligent billing application, the rules engine is used to implement the routing of messages from different topics to different business systems.
Simplify project integration by converting messages from different formats to an easy-to-handle JSON format through the rules engine.
EMQX supports storing MQTT messages to HStreamDB , Redis, MySQL, PostgreSQL, MongoDB, Cassandra, DynamoDB, InfluxDB, OpenTSDB, IoTDB and other databases.
EMQX supports bridging MQTT messages to Kafka, RabbitMQ, Pulsar, RocketMQ, MQTT servers, or other EMQX nodes.
This article will demonstrate how to use the rules engine in EMQX to forward MQTT messages to Kafka.
This document demonstrates how to use the rules engine in EMQX to forward MQTT messages to RabbitMQ.
This article will demonstrate how to use the rules engine in EMQX to forward MQTT messages to Pulsar.
This video will demonstrate how to use the EMQX rule engine to persist the temperature and humidity data to the InfluxDB cloud.
This video will demonstrate how to bridge MQTT data to Kafka using EMQX Cloud eule engine.
This video will create a VPC in Timescale Cloud and bridge data to Timescale Cloud using the EMQX Cloud rule engine.