Platform Architecture

The weeve Platform is designed to orchestrate edge applications. With the simple front-end UI, you can build an application, and deploy it to a selection of edge nodes. The figure below presents a high-level view of the weeve Platform. 
Highest level component view
Figure 1 - Highest level architecture
The front end user interface interacts with the weeve Manager. The weeve Manager manages the databases for users, edge nodes, and other resources. Furthermore, it orchestrates the required operations at the edge. These operations include starting, stopping, and deleting edge applications. The nodes receive orchestration messages and give regular status updates to the weeve Manager. 
A further main component of the platform is the container registry. The registry is a library of all modules, which are the building blocks of edge applications. The state of the registry is inspected by the weeve Manager, and the edge nodes will pull modules as required. 
An edge application is designed to transform raw IoT data into valuable and actionable data insight. In order to orchestrate weeve edge applications, the weeve Agent is installed on the client's hardware device. The weeve Manager comprises the backend orchestration layer, providing a unified API for clients and the edge infrastructure. 
The platform orchestration data can be considered perpendicular to the client IoT data running through an edge application.
The following sections provide more details describing the weeve Agent software running on the edge node devices, and similarly, more details on the backend platform, the weeve Manager. 

Concepts - Previous

The edge explained

weeve Agent & Edge Node Devices

Last modified 1mo ago

Copy link

Contents

Highest level component view