EdgeX 2.0 arrives with improvements in the interface, API, new services and more

After almost two years of the release of the previous version, The new version of EdgeX 2.0 has been released. In this new version a lot of changes are presented of which in addition to bug fixes and updates, we can also find that The web interface has been improved, as well as the API of the microservices it has been reworked, among other things.

For those unfamiliar with EdgeX, I must tell you that this is an open modular platform for interoperability between devices, IoT applications and services. The platform is not tied to specific vendor hardware and operating systems, and is being developed by an independent working group sponsored by the Linux Foundation.

EdgeX'sand characterized by allowing the creation of gateways that connect existing IoT devices and collect data from various sensors. The gateway is dedicated both to organizing the interaction with the devices and to perform the primary processing, aggregation and analysis of the information, acting as an intermediate link between a network of IoT devices and a local control center or a cloud management infrastructure.

Gateways they can also run microservice controllers. Interaction with IoT devices can be organized over a wired or wireless network using TCP / IP networks and specific protocols (not IP).

EdgeX is based on the open IoT stack fuse, which is used in Dell Edge Gateway for IoT devices. The project includes a selection of out-of-the-box microservices for data analysis, security, management, and troubleshooting of various issues.

EdgeX 2.0 Key New Features

In this new version stands out the new web interface that uses the Angular JS framework, with which among the advantages of the new GUI there is ease of maintenance and expansion of functionality, the presence of a wizard to connect new devices, tools to visualize data, a significantly improved interface to manage metadata, the ability to monitor the status of services (memory consumption, CPU load, etc.).

Another important change that occurs is that the API has been completely rewritten to work with microservices, that now does not depend on the communication protocol, it is more secure, well structured (uses JSON) and better tracks the data processed by the service.

Also Application Services capabilities have been expanded, as added support for filtering sensor data by name device profile and resource type, the possibility to send data through a service to multiple recipients and subscribe to multiple message buses and a template is proposed to quickly create your own application services.

It is also highlighted that data can be transferred from device services to data storage and processing services, which can now use the message bus (Redis Pub / Sub, 0MQ or MQTT) without being bound to the HTTP -REST protocol and adjusting QoS priorities at the message broker level.

As for the new device services aggregates are mentioned CoAP with an implementation of the Restricted Application Protocol, GPIO to connect to microcontrollers and other devices, including Raspberry Pi boards, via ports gpio, LLRP which is the implementation of the protocol LLRP (Low Level Reader Protocol) to connect to tag readers RFID and UART (Universal Asynchronous Receiver / Transmitter).

Of the other changes that stand out:

  • Improved reliability and expanded Quality of Service (QoS) tools.
  • A universal module has been implemented to extract secret data from secure storages such as Vault.
  • The number of processes and services that require root privileges in Docker containers has been minimized. Additional protection against using Redis in insecure mode.
  • Simplified configuration of API Gateway (Kong).
  • Simplified device profiles, in which sensor and device parameters are established, as well as information about the collected data.

Finally if you are interested in knowing more about it, you can check the details In the following link.


Be the first to comment

Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.