Service Mesh & Edge Computing — Considerations

How are Service Mesh & Edge Computing Related? Can they help each other?

Figure 1: Latency Sensitivity Across various Edges (source)

Latency being primary driver for edge computing, applications and services need to be developed leveraging the capabilities of edge compute platform. These applications are expected to be cloud native, microservices based, leveraging helper services available on the platform, while providing secure multi-tenant configurations. The partitioning of the functionality must leverage resource awareness in the platform and facilitate performance scalability and security. Mobility and Federation will be important considerations allowing use of services across multiple MEC domains.

Another success factor will be portability across a range of device capabilities, some with hardware acceleration, some without. Paradigm of edge-native applications clearly describe characteristics required for developers to build applications in order to satisfy service offerings at the edge [1]. The reality however is proving to be far more complex for application writers to satisfy plethora of requirements [2]

Where Kubernetes CNI is Limited to…

Microservice architectures are decoupling applications from maintaining & managing infrastructure operations to only perform…