Cloud vs edge: Who serves the Internet-of-Things better?

Zakaria Maamar; Thar Baker; Mohamed Sellami; Muhammad Asim; Emir Ugljanin; Noura Faci

doi:10.1002/itl2.66

Cloud vs edge: Who serves the Internet-of-Things better?

Zakaria Maamar, Thar Baker, Mohamed Sellami, Muhammad Asim, Emir Ugljanin, Noura Faci

School of Arch, Tech and Eng

Research output: Contribution to journal › Article › peer-review

Abstract

Usually announced to the ICT community as rivals in the Internet-of-Things (IoT) context, cloud and edge could work together according to their respective capabilities. Today's IoT applications can be dependent neither on a single technology (either SQL or noSQL) nor on a single operation model (either centralized or decentralized). The multiple challenges are complexity of user scenarios, multiplicity of things, sensitivity of data, etc. This paper raises the question of who serves IoT better? Cloud, only; edge, only; or both together. To answer this question, clouds' and edges' duties are identified and then a set of collaborative scenarios are discussed with respect to these duties.

Original language	English
Article number	e66
Journal	Internet Technology Letters
Volume	1
Issue number	5
DOIs	https://doi.org/10.1002/itl2.66
Publication status	Published - 28 Jun 2018

Access to Document

10.1002/itl2.66

Cite this

@article{4c74422e240a40899fe51cc58ae9c933,

title = "Cloud vs edge: Who serves the Internet-of-Things better?",

abstract = "Usually announced to the ICT community as rivals in the Internet-of-Things (IoT) context, cloud and edge could work together according to their respective capabilities. Today's IoT applications can be dependent neither on a single technology (either SQL or noSQL) nor on a single operation model (either centralized or decentralized). The multiple challenges are complexity of user scenarios, multiplicity of things, sensitivity of data, etc. This paper raises the question of who serves IoT better? Cloud, only; edge, only; or both together. To answer this question, clouds' and edges' duties are identified and then a set of collaborative scenarios are discussed with respect to these duties.",

author = "Zakaria Maamar and Thar Baker and Mohamed Sellami and Muhammad Asim and Emir Ugljanin and Noura Faci",

year = "2018",

month = jun,

day = "28",

doi = "10.1002/itl2.66",

language = "English",

volume = "1",

number = "5",

}

TY - JOUR

T1 - Cloud vs edge

T2 - Who serves the Internet-of-Things better?

AU - Maamar, Zakaria

AU - Baker, Thar

AU - Sellami, Mohamed

AU - Asim, Muhammad

AU - Ugljanin, Emir

AU - Faci, Noura

PY - 2018/6/28

Y1 - 2018/6/28

N2 - Usually announced to the ICT community as rivals in the Internet-of-Things (IoT) context, cloud and edge could work together according to their respective capabilities. Today's IoT applications can be dependent neither on a single technology (either SQL or noSQL) nor on a single operation model (either centralized or decentralized). The multiple challenges are complexity of user scenarios, multiplicity of things, sensitivity of data, etc. This paper raises the question of who serves IoT better? Cloud, only; edge, only; or both together. To answer this question, clouds' and edges' duties are identified and then a set of collaborative scenarios are discussed with respect to these duties.

AB - Usually announced to the ICT community as rivals in the Internet-of-Things (IoT) context, cloud and edge could work together according to their respective capabilities. Today's IoT applications can be dependent neither on a single technology (either SQL or noSQL) nor on a single operation model (either centralized or decentralized). The multiple challenges are complexity of user scenarios, multiplicity of things, sensitivity of data, etc. This paper raises the question of who serves IoT better? Cloud, only; edge, only; or both together. To answer this question, clouds' and edges' duties are identified and then a set of collaborative scenarios are discussed with respect to these duties.

U2 - 10.1002/itl2.66

DO - 10.1002/itl2.66

M3 - Article

VL - 1

IS - 5

M1 - e66

ER -