2016 IEEE/ACM Symposium on Edge Computing (SEC) 2016
DOI: 10.1109/sec.2016.37
|View full text |Cite
|
Sign up to set email alerts
|

Poster Abstract: Hierarchical Serverless Computing for the Mobile Edge

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
10
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 17 publications
(10 citation statements)
references
References 2 publications
0
10
0
Order By: Relevance
“…However, they did not consider the security mechanism in the study. Yan et al [11], De-Lara et al [12], Lakhan et al [13] and Li et al [14] and Li et al [15,16] suggested serverless and container-based application partitioning, resource allocation and scheduling methodology-based linear and dynamic optimization in fog-cloud. The objective is to minimize the execution, energy, response time, and delay and offloading cost of applications.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…However, they did not consider the security mechanism in the study. Yan et al [11], De-Lara et al [12], Lakhan et al [13] and Li et al [14] and Li et al [15,16] suggested serverless and container-based application partitioning, resource allocation and scheduling methodology-based linear and dynamic optimization in fog-cloud. The objective is to minimize the execution, energy, response time, and delay and offloading cost of applications.…”
Section: Related Workmentioning
confidence: 99%
“…Due to the external services, the security of the offloaded data of different users has posed a challenge. Therefore, secure and cost-efficient task scheduling in an edge computing, serverless, decentralized system is becoming a challenge [12].…”
Section: Introductionmentioning
confidence: 99%
“…Due to its use of short, ephemeral functions, and the possibility of invoking a large number of these in parallel, serverless computing is being used for both event-driven workloads, where a VM would be idle most of the time, and for massively parallel, short-term compute, like in data analytics. Example use cases include Internet of Things and edge computing [33], parallel data processing [41], video processing [35], and Web backend APIs [6]. A common property of these workloads is that they are bursty -they make a large number of invocations of a few functions to either tackle bursts in event-driven workloads or exploit data parallelism for analytics.…”
Section: Concurrent Invocations Are Commonmentioning
confidence: 99%
“…These works have identified the challenge of auto-scaling, which is not predictable to the user. When a function is scaled down, the cold start problem can cause latency issues in a constrained environment [10], [47]- [49].…”
Section: Related Workmentioning
confidence: 99%