weeve Manager Backend
Now our attention turns to the weeve Manager, comprised of all backend services. The infrastructure of the weeve manager is managed by weeve in the cloud, or can be deployed to an on-premise location. Figure 3 below presents an expanded view of the weeve manager.
Figure 3 - Manager details
The GraphQL API is at the heart of the weeve-manager. The front-end communicates with the API to initiate edge application deployment or to inquire about the status of the edge compute infrastructure.
The API is linked to a number of generalized data sources. The API, for starters, is in charge of user management. Role-based access control to all resources is part of user management. Second, the API connects data from the edge compute infrastructure, such as the status and metadata of any deployed Weeve agent. The third major category of data concerns the platform's primary resources, such as edge apps, modules, their ownership and provenance, and version histories.
The container registry provides a fourth source of information. Modules are saved and made available to any edge hardware (weeve agent) requesting a certain module, according to access policies.
A publish/subscribe messaging protocol is utilized at the edge. As a result, the GraphQL API sends orchestration orders to edge services, which are in charge of communicating to edge infrastructure. The 'deploy' message, which includes a description of an edge application as well as a list of target edge nodes, is one example of a command message. This message will be safely forwarded to that list of devices thanks to the edge services. The API will get status messages from the edge infrastructure as well.