Functions and Roles of the components

Edge Cluster Environment (Cloud Side, Edge Side)

• 1 EdgeHub
  Websocket clients that interact with cloud services for edge computing (such as Edge Controller as in the KubeEdge architecture). This includes synchronizing cloud-side resource updates to the edge and reporting edge-side host and device state changes to the cloud.
• 2 Edged
  An agent that runs on edge nodes and manages containerized applications.
• 3 EventBus
  An MQTT client that interacts with an MQTT server (Mosquitto) to provide publishing and registration capabilities to other components.
• 4 ServiceBus
  An HTTP client that interacts with an HTTP server (REST), providing HTTP client functionality to cloud components to reach HTTP servers running at the edge.
• 5 DeviceTwin
  It saves device state and synchronizes device state to cloud. It also provides a query interface for the application.
• 6 MetaManager
  The message processor between edged and edgehub is also responsible for storing/retrieving metadata with a lightweight database (SQLite).

Middle Environment

• 1 CloudHub
  A WebSocket server that checks on the alterations from cloud, caches them and send a message to EdgeHub.
• 2 EdgeController
  An extended kubernetes controller that manages edge node and pod metadata so that data can be targeted to specific edge nodes.
• 3 DeviceController
  An extended kubernetes controller that manages devices so that device meta data⁄state data can be synchronized between the edge and the cloud.

Open Source List