Abstract

Currently devices used for data capture often differ from those that are used to subsequently carry out analysis on such data. Many Internet of Things (IoT) applications today involve data capture from sensors that are close to the phenomenon being measured, with such data subsequently being transmitted to Cloud data centers for analysis and storage. Increasing availability of storage and processing devices closer to the data capture device, perhaps over a one-hop network connection or even directly connected to the IoT device itself, requires more efficient allocation of processing across such edge devices and data centers. We refer to these as "vertical workflows" – i.e. workflows which are enacted across resources that can vary in: (i) type and behaviour; (ii) processing and storage capacity; (iii) latency and security profiles. Understanding how a workflow pipeline can be enacted across these resource types is outlined, motivated through two scenarios. The overall objective considered is the completion of the workflow within some deadline constraint, but with flexibility on where data processing is carried out.


Original document

The different versions of the original document can be found in:

https://dblp.uni-trier.de/db/conf/ficloud/ficloud2018.html#RanaSAAB18,
http://orca-mwe.cf.ac.uk/114143,
https://academic.microsoft.com/#/detail/2890976218
http://dx.doi.org/10.1109/ficloud.2018.00058
Back to Top

Document information

Published on 01/01/2018

Volume 2018, 2018
DOI: 10.1109/ficloud.2018.00058
Licence: CC BY-NC-SA license

Document Score

0

Views 0
Recommendations 0

Share this document

Keywords

claim authorship

Are you one of the authors of this document?