Proceedings of the Fifteenth European Conference on Computer Systems 2020
DOI: 10.1145/3342195.3387535
|View full text |Cite
|
Sign up to set email alerts
|

A fault-tolerance shim for serverless computing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
24
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
5
5

Relationship

0
10

Authors

Journals

citations
Cited by 42 publications
(26 citation statements)
references
References 24 publications
1
24
0
Order By: Relevance
“…For example, a platform would automatically resend the request in case of failure of a function execution. Sreekanti et al show that under certain circumstances, a retry based approach to fault tolerance may always not give accurate results, specially where state management is involved via external storage services [124]. They emphasize that the accuracy may be afected in case a parallel execution of a function, views results of a partially executed failed attempt of the same execution.…”
Section: Qos Goalmentioning
confidence: 99%
“…For example, a platform would automatically resend the request in case of failure of a function execution. Sreekanti et al show that under certain circumstances, a retry based approach to fault tolerance may always not give accurate results, specially where state management is involved via external storage services [124]. They emphasize that the accuracy may be afected in case a parallel execution of a function, views results of a partially executed failed attempt of the same execution.…”
Section: Qos Goalmentioning
confidence: 99%
“…The component m i requires a stationary resource r j if MOB(m i ) = 0, and accepts any mobile device if MOB(m i ) = 1. The application owner can define higher MOB (m i ) values if it implements fault tolerance recovery mechanisms, such as alternative execution strategies [33]. This is essential, as the mobility prediction model does not implement any recovery strategy in case of incorrect prediction.…”
Section: Problem Definitionmentioning
confidence: 99%
“…Improvements to serverless platforms. Recent works have proposed serverless-optimized storage and caching solutions (e.g., Pocket [44], Savanna [29, § 3], Cloudburst [85], Aft [84], and HydroCache [97]), security enforcement via information flow control [3], and techniques to optimize the performance and resource usage of serverless platforms [1,42,49,61,65,80,82,85,94]. Kappa automatically benefits from transparent platform improvements, and can exploit new storage services by placing checkpoints and large queue elements there ( § 4).…”
Section: Other Related Workmentioning
confidence: 99%