Management, orchestration and workflow automation
of Edge Computing services: The TANDEM
approach
Konstantinos Vasilopoulos, Vasileios Theodorou, Theodoros Bozios,
Maria-Evgenia Xezonaki and Dimitrios Laskaratos
Emails: {tmpo, konvasilop, maxez, dlaskaratos, theovas}@intracom-telecom.com
Intracom SA Telecom Solutions
Abstract—The distributed computing paradigm that brings
information processing closer to end users and data sources,
i.e., Edge Computing, is growing in popularity and adoption in
many different domains, such as Cloud Computing, Telecommu-
nications, Internet of Things (IoT) and (distributed) Artificial
Intelligence (AI). Despite several efforts towards standardizing
Edge Computing services and their ecosystem-driven interactions,
especially from the telecom world and open-source communities,
automation in deployment, operation and interoperability of
Edge Computing services is still in an immature state, making
practical Edge/IoT scenarios that involve multiple application
services and technologies, complex and cumbersome. This paper
presents our approach of an integrated platform aimed to simplify
the establishment, management, control and monitoring of edge
computing services with a particular focus on the IoT domain.
Central in this effort are the ability to (I) make use of existing
functions and modules in new edge computing services and (II)
to seamlessly integrate service function chain components with
remote backend services and with locally available Edge/IoT
devices for on-device processing. Characteristic examples of
desired functions and local processing tasks, include data stream
analytics, event-driven workflows and Machine Learning tasks
with an emphasis on video stream analysis for Object Detection
and/or tracking, for which we provide a deployment architecture
of our approach.
Keywords- Edge Computing, Function as a Service
(Function-as-a-Service (FaaS)), Service Chain Orchestrator,
Artificial Intelligence (AI), Internet of Things (IoT)
I. I NTRODUCTION
The rapid growth of connected Internet of Things (IoT) de-
vices and the corresponding dramatic increase in data volume,
which is expected to increase even more with the proliferation
of connected devices in 5G networks, is causing latency and
bandwidth bottlenecks, when all data needs to be transmitted
to core nodes for centralized processing. As a response,
Edge Computing [1] has gained traction as an alternative
distributed paradigm, bringing data processing and storage
closer to end users and data sources, exploiting available
compute and networking resources all along the cloud-to-edge
pathway and reducing this way response times and bandwidth,
as well as preserving privacy of data within their generation
environment. Edge Computing is rather complementing than
replacing the already established paradigm of (centralized)
Cloud Computing and organizations that use them together
will benefit from solution synergies that maximize the value
of both centralized and decentralized models [2].
Since infrastructure capacity at the network edge is usu-
ally limited compared to centralized cloud resources, smart
mechanisms are required for the efficient resource manage-
ment and distribution of services between edge nodes and
centralized systems, taking into account functional and non-
functional application requirements. At the same time, such
mechanisms need to account for exploiting the advanced
processing and Artificial Intelligence (AI) / Machine Learning
(ML) capabilities that smart devices, such as smart phones,
smart cameras and robots are nowadays equipped with, which
however present great variability in supported technologies and
protocols. Although several efforts are ongoing for providing
edge-enabling mechanisms and for standardizing the archi-
tectural frameworks and the ecosystem interactions of edge
services (e.g., ETSI Multi-access Edge Computing (MEC) [3]
from the Telecom sector and Linux Foundation Edge1 from
open-source communities), it still remains a challenging and
complex task to automate the deployment, integration and
operation of a set of diverse fit-for-purpose functions at the
edge towards supporting end-to-end practical use cases for
consumers and enterprise customers.
To respond to the above-mentioned edge automation chal-
lenges, we introduce the TANDEM approach, presenting a
novel Edge platform architecture and supporting mechanisms
for its user-centered and robust operation. The aim of TAN-
DEM is to allow end-users to develop, execute and manage
edge services without the cost and complexity of building and
maintaining the infrastructure, while at the same time being
offered the capability to utilize the off-the-shelf, reusable and
integrate-able services it provides. TANDEM supports new
forms of computational models and focuses on an innovative
aspect of edge computing not yet adequately explored, and
specifically the composition of services and applications from
structural elements that can operate on different edge nodes. It
takes into account research approaches and standards for the
design of a system which automates the execution of service
chains and it proposes extensions for the creation of an inte-
grated edge computing system that seamlessly incorporates IoT
functions and AI / ML mechanisms. TANDEM covers business
aspects and manages the transformation of a technical service
into a trade-able service (i.e., a product) by adding elements
such as pricing and Service Level Agreements (SLAs) and the
service and product lifecycles.
1 LF Edge: https://www.lfedge.org/
 As a realization of our approach, the TANDEM platform
supports new serverless and Platform-as-a-Service (PaaS) edge
computing models. Specifically, TANDEM users can use its
existing supporting and elementary services, as well as to
combine existing services with their own custom services
and create complex service/function chains, using the plat-
form’s graphical tool. The target is typical edge computing
environments, such as Industry 4.0, connected vehicles and
smart domains (Smart Home, Smart City, Smart Grid, Smart
Farming etc.) with an emphasis on IoT aspects [4], where
devices’ interconnection and management, as well as multi-
protocol and multi-data type support are common challenges.
In such environments, TANDEM fosters the seamless integra-
tion of data analytics services, using Analytical Processing
and AI / ML technologies to predict future values (e.g.,
of sensor measurements and system usage) and to provide
value-added edge services such as video stream analysis for
Object Detection. Both reusable and custom services on the
TANDEM platform utilize available underlying edge resources
and connected devices, as well as auto-scaling and auto-healing
TANDEM mechanisms, and end-users can easily develop Web
or mobile applications by calling the Application Programming
Interfaces (APIs) of TANDEM platform services.
The remainder of the paper is structured as follows: In
Chapter II, the related work is presented and the differentiation
of TANDEM is explained. Chapter III provides an overview
of the TANDEM approach, the benefits it brings and the
technological concepts that it integrates at the edge. Chapter IV
describes TANDEM system architecture that achieves drastic
simplification of the services development, management, mon-
itoring and extension processes in virtualized edge infrastruc-
tures. Chapter V describes a specific AI (Object Detection) use
case, which TANDEM offers as a service and presents a series
of tools that TANDEM utilizes. Finally, Chapter VI concludes
this paper.
II. R ELATED W ORK
In the context of (Big) Data Analytics automation platforms
for cloud, fog and IoT environments, several relevant EU
research projects have been studied. PrEstoCloud [5] will make
research contributions in the cloud computing and real-time
data intensive applications domains, in order to provide a dy-
namic, distributed, self-adaptive and proactively configurable
architecture for processing Big Data streams. RADON [6]
aims at creating a DevOps framework to create and manage
microservices-based applications that can optimally exploit
serverless computing technologies. RADON applications will
include fine-grained and independently deployable microser-
vices that can exploit Function-as-a-Service (FaaS) and con-
tainer technologies. RAINBOW [7] will design and develop
an open and trusted fog computing platform that facilitates
the deployment and management of scalable, heterogeneous
and secure IoT services and cross-cloud applications (i.e.,
microservices). Finally, ELEGANT [8] aims to develop a novel
software solution that addresses key challenges facing IoT and
Big Data: interoperability, reliability, safety and security.
When it comes to existing Edge / MEC Platform solutions,
there are noteable opensource projects initiated by big vendors,
such as Intel Smart Edge2 for performant and optimized
service deployment on premise and at network edge, and
Edge Gallery3 with additional emphasis on fereration and
interconection of third party applications. In this direction, a
novel approach is also presented in [9], where it is suggested
to abstract the northbound API of Edge Platforms into using a
PaaS edge service delivery model, for seamless interconnection
with 5G Orchestrators.
III. T HE TANDEM A PPROACH
TANDEM focuses on an innovative aspect of edge com-
puting that has not yet been adequately explored, i.e., the
composition of services and applications from structural ele-
ments that may be available or must operate on different edge
nodes. TANDEM uses AI to predict future utilization of each
node’s resources and to decide i) on the service instances that
will be activated in each node and ii) on the edge service
lifecycle management, taking into account the accessibility to
IoT devices from each node, the resource requirements of each
service, the agreement details with the customer (SLA), the
participation of a service in a service chain and service affinity
and co-location requirements as well as the reduction as much
as as possible of energy consumption while satisfying the set
requirements.
A. PaaS, FaaS and Backend-as-a-Service (BaaS) in TANDEM
FaaS has received significant traction during past years, as
a service-based model that alleviates the need for application
developers to worry about underlying infrastructure, auto-
scaling/healing, and various support services for data persis-
tence, authentication, event queuing etc., since all these are
handled by cloud providers. Thus, application developers are
only left with the task of embedding their application business
logic into reusable fragments of code, i.e., the functions,
which are usually orchestrated into event-driven workflow
compositions.
We adopt a similar approach for TANDEM custom services
and we expose a usable FaaS API and corresponding GUI for
end users (i.e., customers) to define their own functions, or
to select among available ones pre-onboarded to the system,
implementing the edge service logic that corresponds to their
application requirements. These functions can interact with
each other, as well as with the readily available TANDEM
support services and TANDEM platform handles all the regis-
tration and discovery of such services, the data storage, event
queuing and dispatching services as well as the composition
and interlinking automation of such services and their opti-
mised deployment on available infrastructure.
To achieve the above-mentioned platform automation fea-
tures, TANDEM handles the exposure and availability of FaaS
Platform support services while introducing an important nov-
elty on their automated deployment. More precisely, TANDEM
advocates a PaaS-based service delivery model, whereby the
enablement and enrichment of available Edge nodes with
specific FaaS support services, is managed in a declarative
fashion that abstracts their deployment and operation details.
2 https://www.intel.com/content/www/us/en/edge-computing/smart-
edge.html
3 https://www.edgegallery.org/en/pc-edgegallery-overview/
The optimization, resilient and secure operation of support
services are also undertaken by the TANDEM platform, which
respects underlying resources’ characteristics and state and
performs all necessary steps for configuring the FaaS-enabled
edge node—from virtualization infrastructure preparation, to
platform services’ readiness and to (FaaS) application-layer
services’ orchestrated activation and interoperability.
Regarding the interoperability of services running on egde
nodes, with centralized (usually legacy) services including
authentication and authorization, master data management,
user and content management, we adopt a BaaS approach.
According to this approach, interfacing from edge nodes
towards backend services is automatically configured and
policed in a secure fashion, using Quality of Service (QoS)-
aware tunneling mechanisms and whenever applicable and
feasible, trade-off analysis (e.g., latency versus bandwidth) is
continuously conducted for deciding whether to launch local
copies of backend services on the edge node.
B. Relation to standards
In relation to standards and architectures, TANDEM is
directly harmonized with most standards, such as ETSI Net-
work Function Virtualization (NFV) Management and Orches-
tration (MANO), in terms of orchestration of the lifecycle
management of PaaS-driven support services as Virtualized
Network Functions (VNFs). In addition, we follow ETSI MEC
principles in terms of the edge computing architecture, as well
as the information model for describing edge services, using
the MEC Application Descriptors (AppD) for the description
of service attributes. and the TM Forum .
Moreover, the TANDEM service model extends the ETSI
MEC model with elements from corresponding models of the
TM Forum4 in terms of the description of the services, the
products created by the services, the product offer, and the
product order. Finally, the service model is also extended with
elements from the Open Service Catalogue Manager [10],
aiming at additional coverage of business aspects, i.e., how
a service is offered to a customer. Thus, TANDEM manages
the transformation of a technical service into a trade-able one
(product) by adding elements such as pricing and SLAs, and
also manages the service, product supply and product order
lifecycles.
C. TANDEM Entities and Roles
The basic entities and roles of TANDEM are described
in Table 1. TANDEM Service Provider installs the TANDEM
(open-source) system on its own infrastructure or that of an
Infrastructure Provider and has revenues from its provision as
a service and from new services requested by Customers. Cus-
tomers can address a TANDEM service provider or have their
own TANDEM system installation. In this case a TANDEM
System Support Service Provider could install and customize
TANDEM and provide daily support.
4 https://www.tmforum.org/resources/interface/tmf623-sla-management-api-
rest-specification-r14-5-0/
TABLE I: TANDEM Entities and Roles
Entity Description
Infrastructure Provides the infrastructure (network, compute and storage), for
Provider TANDEM platform operation. Could be a Telecom Operator
with computing and/or storage resources next to Base Stations
Service Installs the TANDEM system on its own infrastructure or
Provider that of an Infrastructure Provider and offers it as a service.
It makes adjustments or adds functions according to its own
needs (internal use) or its customers’ needs
System Sup- Installs TANDEM on behalf of customers and supports them
port Service daily in its operation, adjustments or additional functions and
Provider services.
Software The TANDEM system prototype will be implemented through
Provider open source software and will be given free access through
free access repositories, e.g. GitHub.
Customer An entity (individual, company) registered on the TANDEM
platform and using its services. i.e., installs their own custom
services that can cooperate with TANDEM services or creates
complex services that will combine functions of existing ones
Fig. 1: AI and Artificial Vision from the core cloud to Edge
clouds
IV. A RCHITECTURE OVERVIEW
The TANDEM architecture takes into account the Euro-
pean Telecommunications Standards Institute (ETSI) NFV [13]
reference architecture as well as the ETSI Multi-access Edge
Computing (MEC) [3] architecture, while adding modules that
support all necessary functions to fulfill the above usage sce-
narios. The key new feature TANDEM introduces, is the ability
to create more complex services and applications by combining
services and integrating devices from different edge hosts or in
the cloud. The architecture of the TANDEM platform is based
on microservices [14]. Its edge nodes (hosts) are organized
in one or more edge clouds, each of which forms a cluster.
Figure 2 shows the levels of TANDEM architecture. It consists
of three basic levels, the System Level, the Edge Computing
Level and the Device Level. An additional intermediate level
between system and edge can be the Edge Cloud Level which
undertakes the management of an edge cloud.
At the System Level reside the TANDEM functions that
coordinate resources (computing, storage and networking),
devices and services of all nodes at the edge. The user can
request the use of services, post their own services as well as
use a combination of third-party services. This level includes
also user management, pricing policies and billing functions.
The Edge Cloud Level, when available, includes the TAN-
DEM Edge Platform Manager with functions for application
life-cycle management as well as monitoring and resource
management and forecasting future resource needs. It contains
the Virtual Infrastructure Manager (VIM), that undertakes
the integrated management of the virtualized infrastructure
(e.g. installation and configuration of virtual machines and
containers). When this level is not available, its functions are
supported by the other 2 levels.
At the Edge Computing/Node Level we can distinguish
the TANDEM Edge Platform, which includes all the services
offered by TANDEM to customers, IoT support services (e.g.
device management services), as well as services that have
been installed by TANDEM customers.
The Device Level includes all the devices connected to
TANDEM (sensors, cameras, etc.). These devices may have
processing capabilities, in which case they could host TAN-
DEM microservices (e.g. robots). TANDEM can receive data
from these devices (e.g. measurements from sensors) and can
in turn send commands or deploy microservices to them.
Fig. 2: The basic levels of TANDEM architecture.
Figure 3 shows the TANDEM architecture based on the
general ETSI MEC architecture, along with its components
which are explained below.
A. System Level
Functions at this level are used by TANDEM’s System
Administrator in order to manage and monitor the use of
resources and devices and the operation of applications on
all TANDEM nodes. Also, by the Customers and Service
Engineers, previously described in Table 1.
This level hosts the TANDEM System Manager that acts
as the coordinator of the functions performed at the TANDEM
level. Specifically, the Manager is responsible for the proper
operation of TANDEM, as it functions as the orchestrator
node for all the TANDEM edge nodes. This level contains
the TANDEM Service Portal which is the only entry point to
third parties in TANDEM functions offered by Edge Orches-
trator and Service Orchestrator. The Tandem System Manager
constitutes of the two components below:
1) Edge Orchestrator: It manages the infrastructure, re-
sources and operation of the services and is used by the
TANDEM system administrator. Its primary functions include
1) service, resource and application management (eg. life-
cycle, migration) at the edge, 2) uploading and registering
application packages on edge hosts and 3) maintaining an
overall picture of the TANDEM system, with its available
resources and topology.
The role of the Edge Orchestrator in an NFV architecture
based on [13] could be played by the NFV Orchestrator
(NFVO) component of the NFV Management and Orchestra-
tion (MANO).
2) Service Orchestrator: It manages all the functions re-
lated to the services provided to the system clients. Cus-
tomers have access to it through the TANDEM Service Portal.
Through the Service Orchestrator customers can use a service,
obtain a list of services provided and their pricing and get in-
formation about the services they use and their current billing.
The System Administrator uses the Service Orchestrator to
centrally manage TANDEM services and related resources.
The basic functions of the Service Orchestrator include
1) managing the services located on edge hosts and their
billing information, 2) connected devices, user and privileges
management, along with pricing models, 3) create service
chains by combining multiple services and 4) selecting edge
hosts for application deployment.
The Service Orchestrator consists of the following mod-
ules:
The TANDEM Service Catalogue is responsible for
registering and storing the services. The information stored
for each service includes resource requirements, its type and
characteristics (functional and quality) and how it is made
available for consumption. The basic functions are a) Service
registration, b) Service discovery and c) Service management.
The Service Chain Orchestrator(SCO) searches the Ser-
vices Catalogue to find the services needed to implement a
specific application. Then, according to the way the services
are defined and their APIs, it is able to perform a composition
of services (service chains). It undertakes the orchestration and
connection of the selected services in order to create a single
application.Connected services can be deployed at different
nodes at the network edge. Through the graphical interface, the
users can see the devices and services available and their APIs,
configure the devices and services, and finally define how the
services are connected to each other and to the devices.
The Service Manager is responsible for the management
of services and their life cycle centrally for all TANDEM
nodes. TANDEM uses AI to predict the future use of resources
at each node and to decide on the instances of the services
that will be activated in each of them and what their life cycle
will be, taking into account the accessibility of IoT devices
from each node, the service resource requirements and the
available resources, the agreement with the customer (SLA)
and the participation of a service in a service chain.
The Central Device Manager is responsible for the overall
device management for all TANDEM nodes. The administrator
has an overview of all devices, their features, their use and
status, and can manage their configuration. Lastly, the User
Management, Pricing and Billing Services. TANDEM has
functions for (a) managing users, user roles and access rights,
(b) defining and managing pricing policy, and (c) creating and
presenting detailed billing information.
3) Service Portal: It is the point to access TANDEM fea-
tures offered by Edge Orchestrator and Service Orchestrator.
Interested parties can use the portal to make their services
 Fig. 3: The architectural components and core technological stack of TANDEM
available, create service chains or gather business and technical
information about the available services.
B. TANDEM Edge Platform Level
At the top level of TANDEM Edge host are services that
can be directly matched to end-user requirements, and can be
the core services in end-user applications, and also be used as
part of a chain of services. These services, called Application
Services, are the basic services offered to the clients and they
are: 1) Data Analytics from IoT devices, 2) Object Detection
from a video stream, 3) Time Series Forecasting from IoT
devices like sensors.
Furthermore, there are also the IoT support services re-
quired to create applications, for example for accessing data
from external devices. These services are: 1) Device discovery
and management services, 2) Scheduling Services, 3) Alerts
& Notifications services and 4) Rules Engine services.
These services can be based on services provided by an
IoT platform such as EdgeXFoundry [15]. A support service
is the Message Queue used for the communication between
services that are part of a complex application. The TANDEM
Edge Host includes also System Services that correspond to
the MEC Necessary Services like the Location service or the
Traffic Management service. There are also services that the
End User has installed in their infrastructure (User Application
Services). These services can communicate with TANDEM
services to use their functions or to offer functions.
The TANDEM Edge Platform Manager has functions for
monitoring and management of one or a cluster of edge
hosts(edge cloud). It handles the service requirements and life
cycle and has AI mechanisms for resource usage prediction.
V. AI USE CASE AND DEPLOYMENT ARCHITECTURE
One modern analytics scenario constituting a candidate for
edge computing is Object Detection. Computer vision and
video analysis are projects that usually require a large amount
of hardware resources as well as vast volumes of data (images
and video streams) that need to be processed in real time,
in most of the cases. The TANDEM platform offers such a
service in the form of applying object detection algorithms to
supervise a parking area. Live video streams from cameras are
used as an input to the TANDEM object detection service and
useful information can be obtained for the operation of the
parking such as detecting the number of free parking spots,
wrongly parked cars, accidents that might require to create
alerts, provide assistance etc, in real time.
Following TANDEM’s approach of deploying object detec-
tion to the edges, it’s possible to take advantage of resources
that might be available at the edges and also minimize require-
ments for bandwidth as only the extracted information of the
services need to travel through the network, in comparison to
the whole video stream. Also, privacy issues are avoided since
the images of people are only handled locally.
An end user may use the TANDEM service catalogue to
find information about the object detection service as well
as the support services (for example an alerting service).
The services can be configured in regard to what output
they will provide (for example the object detection service
can give updates about the number of objects of interest, or
provide a video stream with bounding boxes around regions
of interest) and their interconnection (for example, the rules
that cause an alert of a specific kind). Once the number of
services and the application requirements have been decided,
the TANDEM service chain orchestrator can be used to create
the appropriate connections and deploy the services at the
proper edge nodes. The TANDEM service manager decides the
optimal deployment location, taking into account the available
resources, the expected requirements and the quality of service
requested by the end user. It is also responsible for the service
life cycle. Should one of the services fail, or should the
TANDEM Service Manager conclude that its quality of service
cannot be matched by the current installation, a new instance
will be created in an edge node that fulfills the requirements.
Each time an object detection model is deployed for a new
parking application, the end user may decide to retrain the
model with images from the new deployment site. By provid-
ing annotated images from their own parking lot, the end user
may request the model be retrained on the edge(for privacy
reasons) on the new dataset be added to the TANDEM model
repository to be available to other end users. Additionally, in
the case of more than one deployments of object detection
services in different sites, the services can also work towards
improving their robustness by implementing Machine Learning
schemes such as federated learning.
Figure 3 summarizes the different tools and technologies
used by TANDEM platform in order to allow end users
to construct applications with functionality like the one de-
scribed above. At the lower level, devices communicate with
TANDEM edge level either directly with REST or through
a message queue (MQTT). A TANDEM edge host (edge
level) is managed by Kubernetes [16] and can communicate
with series DBs (eg Prometheus) and visualization tools (eg
Grafana) in order to store and expose the data from the
devices. Moreover, the edge host can utilize a number of
analytics tools (eg TensorFlow [17]) in order to use AI models
provided by TANDEM platform, partake in training them or
even train new ones. At a higher level, the service orchestrator
utilizes workflow engines (eg Argo Workflows [18]) to create
proper relations between services according to a user’s desired
workflow and quality of service.
VI. C ONCLUSION
This paper described in detail a new Edge Computing
platform architecture, which was designed to support practical
application scenarios that could benefit from the existence of
computational, storage and network resources closer to the
data production and consumption points, covering the needs
of different business sectors.
TANDEM is a platform which transfers computing work-
load to the edge taking into account requirements such as
delay, security, reliability and extensibility, while at the same
time it optimally exploits the system’s capabilities.
In conclusion, the TANDEM edge computing system was
designed in order to support the general usage scenarios
listed in TABLE II. The expected benefits of TANDEM will
be demonstrated through the usage scenarios that will be
implemented and concern (a) the remote surveillance using
the Object Detection service, (b) the content caching at the
edge, so as to avoid requesting it from a central server,
and (c) the support of robots operation and cooperation in
Industrial Production in the framework of Industry 4.0. These
use scenarios will be implemented by TANDEM in order to
achieve an evaluation and quantification of the benefits from
a service perspective (e.g. response time reduction).
Future work includes the complete implementation of
TANDEM system elements and the system detailed evaluation
through the selected usage scenarios. Particular emphasis will
be placed on the usability of the Service Chain Orchestrator
(SCO) tool who undertakes the orchestration and connection
of pre-existing services in order to create new, more complex
services and on the introduction of AI in the management of
services and resources.
ACKNOWLEDGMENT
This work is supported by the TANDEM (Function and
Device as a Service Support for Edge Computing) project,
co-financed by the European Union and Greek national
funds through the Operational Program Competitiveness, En-
trepreneurship and Innovation, under the call RESEARCH
CREATE - INNOVATE (project code: T2E∆K-02825)
R EFERENCES
[1] Ashkan Yousefpour, Caleb Fung, Tam Nguyen, Krishna Kadiyala,
Fatemeh Jalali, Amirreza Niakanlahiji, Jian Kong, Jason P. Jue, All
one needs to know about fog computing and related edge computing
paradigms: A complete survey, Journal of Systems Architecture, Volume
98, 2019, Pages 289-330
[2] Bob Gill, David Smith,”The Edge Completes the Cloud: A Gartner
Trend Insight Report”, 14 September 2018 ID: G00360847, Analyst(s):
Bob Gill, David Smith
[3] ETSI MEC, https://www.etsi.org/technologies/multi-access-edge-
computing
[4] Sifakis, J., 2018. System Design in the Era of IoT—Meeting the
Autonomy Challenge. arXiv preprint arXiv:1806.09846.
[5] Proactive Cloud Resources Management at the Edge for
Efficient Real-Time Big Data Processing (PrEstoCloud),
https://cordis.europa.eu/project/id/732339
[6] Rational decomposition and orchestration for serverless computing
(RADON), https://radon-h2020.eu/overview/
[7] An open, trusted Fog Computing Platform facilitation the deploy-
ment, orchestration and management of scalable, heterogeneous and
secure IoT services and cross-cloud apps (RAINBOW), https://rainbow-
h2020.eu/rainbow-platform/
[8] Secure and Seamless Edge-to-Cloud Analytics (ELEGANT),
https://cordis.europa.eu/project/id/957286
[9] A. Lekidis, V. Theodorou, N. Psaromanolakis, C. Guerrero and D.
R. Lopez, PiEdge: An Edge-Driven PaaS Model for Network Slicing
Automation, 2021 Joint European Conference on Networks and Com-
munications & 6G Summit (EuCNC/6G Summit), 2021, pp. 335-340
[10] Open Service Catalogue Manager,
https://openservicecatalogmanager.org/
[11] Qi Xia, Winson Ye, Zeyi Tao, Jindi Wu, Qun Li, “A Survey of Federated
Learning for Edge Computing: Research Problems and Solution”, To
appear in: High-Confidence Computing (2021)
[12] Bosch IO whitepaper: Edge computing for IoT: A guide on
how edge computing complements the cloud in IoT, November
2020, [Online]: https://bosch.io/wp-content/uploads/20201127 White-
Paper Edge-computing EN.pdf
[13] ETSI GS NFV-IFA 011 V2.1.1, “Network Functions Virtualisation
(NFV); Management and Orchestration; VNF Packaging Specification”,
October, 2016
[14] The microservice architecture, https://microservices.io/
[15] The Preferred Edge IoT Plug and Play Ecosystem-Enabled Open
Software Platform, https://www.edgexfoundry.org/
[16] Production-Grade Container Orchestration, https://kubernetes.io/
[17] An end-to-end open source machine learning platform,
https://www.tensorflow.org/
[18] Argo Workflows - The workflow engine for Kubernetes,
https://argoproj.github.io/argo-workflows/