The Emerging Landscape of Edge Computing

Abstract

Edge computing is a trending notion introduced a decade ago as a new computing paradigm for interactive mobile applications. The initial vision of the edge was a multi-tenant resource that will be used opportunistically for low-latency mobile applications. Despite that vision, we see in practice a different set of applications, driven by large-scale enterprises that have emerged and are driving realworld edge deployments today. In these applications, the edge is the primary place of storage and computation and, if network conditions allow, the cloud is opportunistically used alongside. We show how these enterprise deployments are driving innovation in edge computing. Enterprise-driven scenarios have a different motivation for using the edge. Instead of latency, the primary factors are limited bandwidth and unreliability of the network link to the cloud. The enterprise deployment layout is also unique: on-premise, single-tenant edges with shared, redundant outbound links. These previously unexplored characteristics of enterprise-driven edge scenarios open up a number of unique and exciting future research challenges for our community.

Pruning Edge Research with Latency Shears

“…Efforts, therefore, should instead focus on those regions for deployment. Noghabi et al [51] lists some application-specific deployments where edge may offer benefits even in developed regions, e.g. handling video feeds from traffic cameras.…”

Rethinking Operators Placement of Stream Data Application in the Edge

“…For each node v, s v is randomly chosen from 5 to 10. For each edge uv, the bandwidth is randomly chosen between 10 and 100 Mbps and are of the same magnitude as the ones used in [11] for Edge environments. Application.…”

“…The mutual low-latency objective for both Data Stream Processing (DSP) and Edge environments has resulted in a continuous growth of DSP deployments on Edge or Fog environments [11]. The success of DSP deployments in the Edge relies on operators placements and the ability to sustain low latency.…”

Instability in Geo-Distributed Kubernetes Federation: Causes and Mitigation

“…located in different regions of the same cloud provider or multiple cloud providers, KubeFed assumes high reliability of the network connectivity between the control plane and the managed clusters. However, such assumptions are not met in many fog computing environments [4]. As a result, static configurations, including the default values of the configuration parameters for both Kubernetes and KubeFed are not necessarily well-suited to the case of geo-distributed fog computing infrastructures.…”