2019 IEEE Global Communications Conference (GLOBECOM) 2019
DOI: 10.1109/globecom38437.2019.9014114
|View full text |Cite
|
Sign up to set email alerts
|

A Microservice Store for Efficient Edge Offloading

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
11
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
5
1

Relationship

2
4

Authors

Journals

citations
Cited by 6 publications
(11 citation statements)
references
References 13 publications
0
11
0
Order By: Relevance
“…Discovery mechanisms that rely on central repositories (e.g., as in [50]) clearly do not scale. The same is true for the control and management of the infrastructure (e.g., as in [110]). Unified and scalable discovery and management become even more challenging if we consider edge sites owned by different stakeholders.…”
Section: Multi-access Edge Computingmentioning
confidence: 97%
See 1 more Smart Citation
“…Discovery mechanisms that rely on central repositories (e.g., as in [50]) clearly do not scale. The same is true for the control and management of the infrastructure (e.g., as in [110]). Unified and scalable discovery and management become even more challenging if we consider edge sites owned by different stakeholders.…”
Section: Multi-access Edge Computingmentioning
confidence: 97%
“…Golkarifard et al [109] present a framework that supports both cloud and edge offloading for wearable computing applications. Orthogonal to those approaches, Gedeon et al [110] have suggested the concept of a repository where the services to be offloaded are stored and, thus, do not need to be transferred from the client to the surrogate.…”
Section: ) Offloading Mechanismsmentioning
confidence: 99%
“…Microservice offloading may be demanded due to several reasons: (1) demand change, (2) host node (or container) resources running low, and (3) security and privacy. Furthermore, depending on the application, the microservice does not offload as a whole but only as a task, a thread, or a workload [55,56]. Figure 4 shows an example where an orchestrator offloads a Microservice (µService A running in Node A) to another host (Node B).…”
Section: Architecting Microservicesmentioning
confidence: 99%
“…Consequently, a microservice must be capable of working with a plethora of different technologies, a concept called polyglot microservice [43]. Thus, several database systems can be used in a microservice architecture, like Cassandra [57], InfluxDB [136,147], MySQL [55,78], MongoDB [18,29]. Moreover, the microservices are developed using different programming languages and frameworks such as, Python [55,78,79,146,136,81,139,54,140,142,121,28], Java OSGi [110,125], SpringBoot [71,146,115], Java [41,29,79,128,53,94], Golang [18,146,84], Node.JS [125,137], C++ [78,79,140], R [17], and even pure C [126].…”
Section: Conclusion Validitymentioning
confidence: 99%
“…As a numeric metric, we can for example quantify the error in the computation, i.e., the deviation from a numeric optimum or the accuracy of the result. To realize our concept, we implement the required mechanisms for adaptable microservices into our previously developed Edge Computing framework [70]. Figure 2 depicts an overview of this design.…”
Section: The Concept Of Adaptable Microservicesmentioning
confidence: 99%