2019 IEEE 12th International Conference on Cloud Computing (CLOUD) 2019
DOI: 10.1109/cloud.2019.00068
|View full text |Cite
|
Sign up to set email alerts
|

Industrial-Scale Stateless Network Functions

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
5
2

Relationship

2
5

Authors

Journals

citations
Cited by 14 publications
(7 citation statements)
references
References 9 publications
0
7
0
Order By: Relevance
“…As for the technical migration overhead, we argue that stateless [26] application components can be migrated with minimal extra resources. The stateless design, of course, must be supported by a distributed cloud database [24,25], which transforms the punctual migration overhead into a continuous synchronization of application states onto multiple database instances running on nodes potentially hosting the stateless application, which leads to an extra consumption in terms of compute, memory and network resources.…”
Section: Complexity Analysis Of Pod Migration Calculationmentioning
confidence: 99%
See 2 more Smart Citations
“…As for the technical migration overhead, we argue that stateless [26] application components can be migrated with minimal extra resources. The stateless design, of course, must be supported by a distributed cloud database [24,25], which transforms the punctual migration overhead into a continuous synchronization of application states onto multiple database instances running on nodes potentially hosting the stateless application, which leads to an extra consumption in terms of compute, memory and network resources.…”
Section: Complexity Analysis Of Pod Migration Calculationmentioning
confidence: 99%
“…The standard way of achieving these goals is to decouple the life-cycle of important application states from the life-cycle of individual application instances: states, and data in general, are written to and read from cloud databases, deployed close to the application code. Rooted in cloud-native computing, the stateless design outsources the state embedded in computing entities, e.g., virtual machines, containers, Pods, virtual network functions, to a dedicated state storage layer, facilitating elastic scaling and resiliency [26]. In [26] the authors propose a system design that can be adapted to any cloud application without the need for complex coordination among the network control, the stateless application elements, and the state storage backend.…”
Section: Latency-critical Cloud-native Applications and The Edge Cloudmentioning
confidence: 99%
See 1 more Smart Citation
“…The main goal of our proposed system design is to enable FaaS functionality for users, with both horizontal scaling, and with small function composition and data access overhead, while retaining the flexibility and security of the currently available platforms. Our key observation is that local data access and function invocations within the same server are typically an order of magnitude faster than remote ones [35], [36]. Some illustrative overhead values can be found in Table II.…”
Section: A Motivation For Co-locationmentioning
confidence: 99%
“…With the advent of 5G, there is a strong drive in the industry to make applications more cloud-native [5,6]-that is, transform them so that they are stateless. The advantage of this approach is that the applications become independent of the underlying infrastructure (cloud vendor agnosticism), which paves the way for novel cloud, edge, and mobile management systems and use-cases, like vendor-agnostic resource consolidation [7], resource-aware cloud service admission control [8], and real-time (low-latency) 5G-enabled industrial IoT [9].…”
Section: Introductionmentioning
confidence: 99%