Table of Contents
Fetching ...

FlowUnits: Extending Dataflow for the Edge-to-Cloud Computing Continuum

Fabio Chini, Luca De Martini, Alessandro Margara, Gianpaolo Cugola

TL;DR

FlowUnits address the gap between traditional dataflow systems and edge-to-cloud computing by adding locality awareness, resource-aware placement, and dynamic update capabilities. The approach defines FlowUnits and region-aware deployment with capability predicates, implemented as an extension of Renoir. Evaluation demonstrates locality-aware deployments mitigate inter-zone communication bottlenecks and improve resilience under varying network conditions. The work enables deploying unified data processing pipelines across edge, fog, and cloud layers while maintaining dataflow simplicity.

Abstract

This paper introduces FlowUnits, a novel programming and deployment model that extends the traditional dataflow paradigm to address the unique challenges of edge-to-cloud computing environments. While conventional dataflow systems offer significant advantages for large-scale data processing in homogeneous cloud settings, they fall short when deployed across distributed, heterogeneous infrastructures. FlowUnits addresses three critical limitations of current approaches: lack of locality awareness, insufficient resource adaptation, and absence of dynamic update mechanisms. FlowUnits organize processing operators into cohesive, independently manageable components that can be transparently replicated across different regions, efficiently allocated on nodes with appropriate hardware capabilities, and dynamically updated without disrupting ongoing computations. We implement and evaluate the FlowUnits model within Renoir, an existing dataflow system, demonstrating significant improvements in deployment flexibility and resource utilization across the computing continuum. Our approach maintains the simplicity of dataflow while enabling seamless integration of edge and cloud resources into unified data processing pipelines.

FlowUnits: Extending Dataflow for the Edge-to-Cloud Computing Continuum

TL;DR

FlowUnits address the gap between traditional dataflow systems and edge-to-cloud computing by adding locality awareness, resource-aware placement, and dynamic update capabilities. The approach defines FlowUnits and region-aware deployment with capability predicates, implemented as an extension of Renoir. Evaluation demonstrates locality-aware deployments mitigate inter-zone communication bottlenecks and improve resilience under varying network conditions. The work enables deploying unified data processing pipelines across edge, fog, and cloud layers while maintaining dataflow simplicity.

Abstract

This paper introduces FlowUnits, a novel programming and deployment model that extends the traditional dataflow paradigm to address the unique challenges of edge-to-cloud computing environments. While conventional dataflow systems offer significant advantages for large-scale data processing in homogeneous cloud settings, they fall short when deployed across distributed, heterogeneous infrastructures. FlowUnits addresses three critical limitations of current approaches: lack of locality awareness, insufficient resource adaptation, and absence of dynamic update mechanisms. FlowUnits organize processing operators into cohesive, independently manageable components that can be transparently replicated across different regions, efficiently allocated on nodes with appropriate hardware capabilities, and dynamically updated without disrupting ongoing computations. We implement and evaluate the FlowUnits model within Renoir, an existing dataflow system, demonstrating significant improvements in deployment flexibility and resource utilization across the computing continuum. Our approach maintains the simplicity of dataflow while enabling seamless integration of edge and cloud resources into unified data processing pipelines.

Paper Structure

This paper contains 7 sections, 3 figures.

Figures (3)

  • Figure 1: Example of dataflow logical and execution graph.
  • Figure 2: Organization of hosts into zones, identified by their layer and location.
  • Figure 3: Execution time ratio of a Renoir deployment vs a FlowUnit deployment, varying network bandwidth and delay between zones.