EMQX Newsletter 2022-07｜EMQX 5.0 officially released, 2 new database integrations added to EMQX Cloud

Last month, the latest milestone version v5.0.0 of EMQX was officially released . This release brings many groundbreaking updates and improvements. Currently, the EMQX team is iterating on subsequent versions at a rate of one version every two weeks to quickly fix known issues and incorporate more features. In addition, the EMQX team has made great progress in community communication and multiple new functions this month.

In terms of cloud services, EMQX Cloud has added support for two external integrated databases, and users will have more choices for data persistence. EMQX Kubernetes Operator has released a new version, which also supports synchronous adaptation to EMQX 5.0. In addition, it also implements deployment support for edge computing products such as eKuiper and Neuron .

EMQX

Rules engine RocketMQ supports authentication and ACL

RocketMQ enabling access control can improve the security and confidentiality of the system. The EMQX team recently added authentication and ACL capabilities to RocketMQ in the rule engine to connect to RocketMQ with access control enabled. This feature will be updated in the near future. Officially launched.

SASL/SCRAM authentication for Kafka

Kafka supports SASL/SCRAM authentication. SCRAM (Salted Challenge Response Authentication Mechanism) is one of the SASL mechanisms. It solves security problems by performing traditional mechanisms of username/password authentication (such as PLAIN and DIGEST-MD5).

EMQX will support Kafka's SCRAM-SHA-256 and SCRAM-SHA-512 authentication, which can be used with TLS to provide more secure Kafka data integration. This feature will also be officially launched in a recent version update.

Support for checking configuration files via CLI

We have added the configuration file checking capability for EMQX. When the configuration needs to be reloaded at runtime, the modified configuration file (including the plugin configuration) can be checked for syntax errors through the CLI. This command is very important to avoid the Failed to start due to configuration errors.

4.3 & 4.4 Maintenance Release Upgrade

EMQX open source version v4.3.16 & v4.4.5 and enterprise version v4.3.11 & v4.4.5 have been officially released early last month, bringing many known bug fixes such as inaccurate memory calculation of EMQX in Linux systems, as well as HStreamDB integration, Several feature improvements such as exclusive subscriptions.

For more information, please check the Release Note of the corresponding version for more detailed information: EMQX v4.4.5 , EMQX Enterprise v4.4.5 .

At the same time, the development of the next maintenance version of 4.3 & 4.4 is now nearing completion and will be released in the near future, so stay tuned.

EMQX 5.0 product interpretation series of articles and live broadcast

In order to facilitate users to better understand the technical details and product value of EMQX 5.0, the EMQX team has launched a series of articles on product interpretation of version 5.0. At present, "How EMQX 5.0 under the new structure of Mria + RLOG realizes 100 million MQTT connections" and "MQTT over QUIC: the next-generation IoT standard protocol injects new impetus into message transmission scenarios" , we will also share EMQX 5.0 in the future. New progress in data integration, authentication and access control, plug-in expansion, etc., please pay attention to the follow-up push.

EMQX Cloud

Console deployment log monitoring new revision

The log monitoring in the deployment details has been revised and optimized. The previous logs can only be searched and filtered in the time range and cluster nodes. The key log information needs to be searched by the user, which is not easy to analyze. The revised log module reconstructs the log parsing and search capabilities, and provides log information of multiple levels of EMQX two nodes [emqx-node-1] and [emqx-node-2], which can be accessed from ClientID, ClientIP, Username, Topic, resource, and rule ID can be searched and analyzed in multiple dimensions, and can also be filtered according to different error types. Error types include: data integration , client, message , module , EMQX internal error , etc.

For details, please refer to: EMQX Cloud update: log analysis adds more parameters, monitoring operation and maintenance is more worry-free

Data integration supports Alibaba Cloud Tablestore Tablestore

Alibaba Cloud Tablestore provides serverless table storage services for massive structured data, and provides a one-stop IoTstore solution for in-depth optimization of IoT scenarios. It is suitable for structured data storage in scenarios such as massive bills, IM messages, Internet of Things, Internet of Vehicles, risk control, and recommendation. It provides low-cost storage of massive data, millisecond-level online data query and retrieval, and flexible data analysis capabilities.

EMQX Cloud has supported data persistence to Alibaba Cloud Tablestore in data integration, providing users with the necessary data persistence solutions. Check out here to learn more.

Data integration supports streaming database HStreamDB

HStreamDB is a stream database open sourced by EMQ that manages the entire life cycle of access, storage, processing, and distribution of large-scale real-time data streams. It uses standard SQL (and its streaming extensions) as the main interface language, with real-time as its main feature, and aims to simplify the operation and maintenance of data flow and the development of real-time applications.

EMQX Cloud is the first to support forwarding and storing device-side data to HStreamDB, providing users with a new data persistence solution. Check out here to learn more.

EMQX Kubernetes Operator

v1.2.3 released

The following new features are available in the EMQX Operator 1.2.3 release in July:

• The port adjustment pod will not restart, and the service stability is further improved
• By adjusting the listener in the EMQX Dashboard, it can be automatically updated without changing the K8s related configuration
• Increase the EMQX cluster status field to observe if the cluster is ready
• Allow users to customize (Dashboard and Management) account passwords

• Allow users to add custom Containers

  At the same time, there are the following improvements and optimizations:

• Optimized the problem of configmap update file delay
• Fixed a possible split-brain problem in EMQX in the K8s environment

EMQX 5.0 support

• Implement EMQX non-core node deployment through Deployment (core still uses sts)
• Support port dynamic scaling function

Complete cloud environment verification

We have used EMQX Operator to conduct cluster building tests on mainstream cloud platforms. The completed ones are:

• Build an EMQX cluster on AWS eks to achieve test verification of 1 million connections and 500,000 TPS
• Build an EMQX cluster on Huawei cce to achieve test verification of 2 million connections and 1 million TPS
• Build an EMQX cluster on Alieks to achieve test verification of 1 million connections and 500,000 TPS

Support edge computing product deployment

EMQ's edge computing products (edge streaming engine eKuiper, edge industrial protocol gateway software Neuron) have supported deployment through Helm, and high availability has been verified through KubeEdge.

Copyright statement: This article is original by EMQ, please indicate the source when reprinting.

Original link: https://www.emqx.com/zh/blog/emqx-newsletter-202207