Deployment patterns
Edgecell empowers multiple patterns for deploying the management of edge nodes.
In the following diagrams, Edgecell means all the server software (services) that manage and monitor nodes. It includes a Git server and Edge Private Network (EPN) orchestrator.
Basic pattern
In the most basic pattern, Edgecell hosts all the software as a service in its own cloud. The deployer organization has an Edgecell instance that mirrors certain repos from the provider's git server. Each node does pull requests via EPN from the deployer's Edgecell instance in the cloud.
There can be multuple locations and each location can have multiple nodes. We just show a single location and node in these diagrams for simplicity and clarity.
We recommend this pattern for getting started and migrating to other patterns as needed as workload increases.
Deployer cloud pattern
In this pattern, the deployer organization installs Edgecell services in their own virtual private cloud (VPC). The service mirrors repos from Edgecell. All edge nodes read from the deployers services via EPN.
Deployer regional cloud pattern
If the deployer has thousands of nodes across the globe, it may make sense to have nodes route to regional cloud.
Deployer onsite pattern
The deployer can also install Edgecell services onsite. This pattern is particularly effective for manufacturing.
These patterns can be combined. For instance, a global manufacture may have regional cloud feeding to multiple onsite Edgecell installations.
Regional cooperation pattern
EPN can enable direct location to location connections between nodes. This pattern is particularly effective for retail. For instance, being able to see inventory levels of nearby stores.
This pattern also works for military. One can quickly create ad hoc task force of directly cooperating nodes (eg drones).