Shulou(Shulou.com)06/01 Report--

What are the functions of EMQ X Enterprise 3.4.0? I believe many inexperienced people don't know what to do about it. Therefore, this article summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

EMQ X Enterprise enterprise-class Internet of things MQTT message platform supports one-stop access to millions of Internet of things devices, MQTT&CoAP multi-protocol processing, and low-delay real-time message communication. Support SQL-based built-in rule engine, flexibly process / forward messages to back-end services, store message data to various databases, or bridge enterprise middleware such as Kafka, RabbitMQ, Pulsar, etc. EMQ X Enterprise is suitable for various Internet of things application scenarios to help enterprises quickly build Internet of things applications and support arbitrary deployment of public cloud, private cloud, physical machine, container / K8S.

Brand-new Dashboard UI

In previous versions of EMQ X, around MQTT message access, EMQ expanded a series of basic functions for convenient and rapid construction of Internet of things applications, such as authentication / ACL, data persistence and message bridging (enterprise version) and integrated into Dashboard.

In order to support the introduction of more new features and the simultaneous improvement of the ease of use of the system and the ability of monitoring and management, the EMQ development team took the lead in designing a new Dashboard UI for the enterprise edition, adjusting the interface style, operability, application structure and data presentation focus, and committed to creating a fully functional IoT Hub management platform:

Achieve full control of the status of the EMQ X cluster and add a real-time display interface for key operating indicators

Provide operation metrics aggregation statistics and persistence records and front-end display, cluster history messages, connections, topics, subscription indicators at a glance

Strengthen commercial functions, display License authorization information, including issuing company, number of authorized lines, expiration date, enterprise operation and maintenance is more convenient and quick to use.

Achieve basic device management functions, simplify connection information, support online kicking out of devices, viewing and managing device subscription information, manually adding subscription relationships, etc.

Optimize the rule creation steps, provide a creation wizard for enterprises to quickly learn and master, and clarify the application relationship of the rule engine

Add alarm management, display the current number of alarms globally, and provide historical alarm records for troubleshooting, making it easy to find and solve problems to avoid the risks caused by alarms.

Dashboard supports hot configuration parameters

Prior to 3.4.0, all changes made to the main EMQ X configuration etc/emqx.conf need to be restarted before they can be applied, such as anonymous authentication (allow_anonymous), ACL switches and policies (enable_acl), connection statistics (enable_stats) and so on.

After EMQ evaluation, dozens of configuration items that do not affect system stability but have hot configuration requirements are listed, and hot configuration functions are provided in Dashboard and REST API.

Dashboard supports cluster management

In this version, Dashboard adds a cluster management and operation feature, and the visual interface provides cluster invitation and kick-out features in manual cluster mode; other automatic cluster modes display cluster parameters, which greatly facilitates monitoring and management and reference configuration of new nodes.

Powerful Schema Registry

In the application of the Internet of things, in order to take into account the network transmission performance and device processing capacity, many underlying devices rely on message data in a relatively low-level, concise format. Broker needs to deal with coding and decoding a variety of compressed binary data formats, industry-specific data formats and even private data formats.

The previous processing scheme is to bridge this kind of data to the application system, and then send it back to Broker for processing after the application system coding and decoding. The whole architecture integration is very complex, and there are some problems such as high processing delay and unclear processing logic.

In order to solve this pain point, EMQ designed and developed a set of Broker built-in, real-time codec system Schema Registry. Schema Registry supports Avro, Protocol Buffers and third-party codec service message parsing.

Schematic diagram of Schema in conjunction with the rules engine:

Currently, EMQ X supports three protocol parsing methods:

Avro is a remote procedure call and data serialization framework developed within Apache's Hadoop project. It uses JSON to define data types and communication protocols, uses compressed binary format to serialize data, and EMQ X Enterprise built-in support

Protocol Buffers is a lightweight and efficient structured data storage format that can be used for structured data serialization, or serialization. It is very suitable for data storage or RPC data exchange format. Can be used in communication protocols, data storage and other fields of language-independent, platform-independent, extensible serialized structural data format, EMQ X Enterprise built-in support

The third-party codec service transmits the original message data to the external codec service through TCP and HTTP communication, waits for the codec data to be returned, and then carries on the subsequent logic. The third-party service can be a self-built codec gateway or even a hot Serverless application in cloud computing.

The figure above shows that we have created a new codec service, which is used in the rule engine as follows:

SELECT decode ('schema:1.0', payload) as payloadFROM "message.publish" WHERE topic = ~' t _ blank'

Using Schema Registry combined with the function of rule engine, the codec rules are created directly through decode and encode function calls in the rule engine, which greatly simplifies the integration ability of message applications.

The support of China National Standard Agreement JT/T808 for vehicle networking.

The new vehicle networking protocol is connected to JT/T808, the full name is "JT/T808-2013 road transport vehicle satellite positioning system Beidou compatible vehicle terminal communication protocol technical specification", this protocol is a strong industry communication protocol. Through the adaptation of this protocol, EMQ has established a complete industry / private protocol access development model, which provides a successful template for subsequent customized development of other protocols.

Schematic diagram of JT/T808 protocol access architecture:

New version function planning

In future releases, the functionality of Dashboard will continue to be enhanced, and it is planned to continuously adjust and optimize to achieve the following functional improvements:

Optimize plug-in configuration: for security reasons, plug-in configuration on Dashboard is not persisted to Broker. Stable configuration needs to be manually written to the configuration file after successful debugging. With the improvement of the security of Dashboard and related API, the subsequent EMQ plans to persist the plug-in configuration on the interface, and there is no need for additional operations on the configuration files in most scenarios.

Provide plug-in function management interface: at present, the management of plug-ins by Dashboard is limited to configuration. Many plug-ins such as emqx_auth_clientid, emqx_auth_username and emqx_configs have corresponding business functions and usage in addition to basic configuration. EMQ will be adapted to development in Dashboard one by one, providing plug-in configuration and use interface.

Plug-in hot installation and hot upgrade: upload the binary plug-in package in Dashboard to achieve plug-in installation and upgrade without downtime. Hot installation hot upgrade is mainly used to deal with important fixes and small-scale feature upgrades of EMQ X.

Custom alarm implementation: user-defined alarm rules and alarm trigger methods will be supported in the future to ensure that alarm reminders are not offline.

After reading the above, have you mastered the functions of EMQ X Enterprise 3.4.0? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.