release , an open modular platform for enabling interaction between IoT devices, applications, and services. The platform is not tied to specific vendor hardware or operating systems and is developed by an independent working group under the auspices of the Linux Foundation. The platform's components under the Apache 2.0 license.
EdgeX allows the creation of gateways that connect existing IoT devices and collect data from various sensors. The gateway organizes interaction with devices and performs initial processing, aggregation, and analysis of information, serving as an intermediary between the network of IoT devices and a local management center or cloud management infrastructure. Processors can also run on the gateways, formatted as microservices. Interaction with IoT devices can be organized over wired or wireless networks using TCP/IP networks and specific (non-IP) protocols.
Gateways of different purposes can be combined into chains; for example, a first-level gateway can handle device management tasks and ensure security, while a second-level gateway (fog server) can store incoming data, perform analytics, and provide services. The system is modular, so the division of functionality into separate nodes is done based on load: in simple cases, one gateway is sufficient, while larger IoT networks may require the deployment of an entire cluster.
At the core of EdgeX is the open IoT stack , which is used in gateways for IoT devices . The platform can be installed on any hardware, including servers based on x86 and ARM CPUs running Linux, Windows, or macOS. Programming languages such as Java, JavaScript, Python, Go, and C/C++ can be used for microservices development. An SDK is provided for developing drivers for IoT devices and sensors.
The project includes a collection of ready-made microservices for data analysis, security, management, and various task solutions.
The release of 1.0 summarizes two years of development and testing, marks the stabilization of all major APIs for standardization of edge applications, and acknowledges readiness for widespread adoption.
Key :
- Support for Redis and MongoDB for all services using databases. Simplification of storage layer replacements for persistent data storage.
- Addition of application services and SDKs for their creation. Application services refer to handlers for preparing data before sending it to the final server. In the future, application services will replace export services and are currently positioned as a tool for solving smaller export tasks that are processed more efficiently.
- Expanded system management tools now include the ability to track the load created by the service on the CPU, the status of data processing, and other metrics.
- Consideration of a correlation identifier, allowing tracking of incoming data from sensors at all stages until export, simplifying debugging and monitoring.
- Support for receiving, using, and exporting binary data in the CBOR format.
- Inclusion of tools for unit testing and automated security checks.
- Preparation of a new framework for visual assessment of resource consumption and overall system behavior.
- Engagement of new and improved SDKs for developing services that interact with devices and sensors in Go and C languages.
- Improvement of tools for deploying configurations, scheduling, device profiles, API gateways, and secure storage of confidential data.
Source: opennet.ru
