Blog

We will start from scratch using the handwriting YAML file method to deploy a K8S cluster of EMQX MQTT broker, and analyze details and techniques of the deployment.

Kuiper 0.5.0 added count window which can be used for window analysis based on count, and more JSON functions support.

Kuiper 0.4.1 supports modifying EdgeX MQTT message bus configurations via Docker environment variables, supports plugin multi-instances and http_pull source.

This article describes how to use the EMQX Kuiper rules engine and how to implement controlling IoT devices according to the analysis result.

MQTT 5.0 client tool - MQTT X v1.3.1, which adds an enable item of strictly validating certificate and supports for more attributes of MQTT 5.0.

In EdgeX Geneva, EMQX Kuiper - an SQL based rule engine is integrated with EdgeX. The tutorial introduces how to use Kuiper to process the data from EdgeX.

EMQX provides a complete IoT private TCP protocol access solution through server adaptation and device-side adaptation.

Kuiper 0.4.0 now has the capability of supporting more complex plugin; Support template feature for all sinks, so users can customize complex output data.

Kuiper plugin is based on the plugin mechanism of Golang, users can build loosely-coupled plugin applications, dynamic loading and binding when it is running.

The message retention function of [EMQX MQTT Broker](https://emqx.io) is implemented by the `emqx_retainer` plugin, which is enabled by default. By modifying the configuration of the` emqx_retainer` plugin, you can adjust the EMQX Broker's retention message Location, restrict the number of retained messages and maximum payload length, and adjust the expiration time of retained messages.

The Kuiper & EdgeX integration work is almost completed, Kuiper will be integrated with EdgeX nightly Docker composer files soon. Kuiper 0.3.1will be released with EdgeX officially.

Integration with EdgeX, support for Schemaless flow definition, and FVT test case enhancement are added in this version