Should applications run on the edge or in the cloud?
In many cases, the answer is “both”. Some components are better served from the edge, with low latency, and other components are better deployed in a central cloud, where reliability, performance/cost ratio, and storage volumes are higher.
It is also very common to let many application instances run at the edge and have a central counterpart, or controller, running in the cloud.
How does edge and cloud help with (GDPR) compliance?
Compliant Kubernetes, which is available on EU-based cloud infrastructure, helps address legal requirements due to GDPR. Avassa’s edge computing fits naturally into that, by processing data closely to its origin.
For instance, an Internet of Things (IoT) connected device could emit data to an edge compute node, have it processed there and getting control instructions from it in return. The edge node then reports to a cloud service, from which it might get updated instructions on how to process and control data in the future, based on federated machine learning.
How do I design my application for the edge and cloud?
Designing a two-tiered application, with an edge and a cloud tier, requires answers to: how to determine where data is, what significantly impacts data at the edge vs. in the cloud, and how to interconnect the two.
Read the whole whitepaper to understand these intricacies and more!