2019
DOI: 10.1016/j.future.2019.05.062
|View full text |Cite
|
Sign up to set email alerts
|

A cloud-agnostic queuing system to support the implementation of deadline-based application execution policies

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
14
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
7
1

Relationship

3
5

Authors

Journals

citations
Cited by 15 publications
(14 citation statements)
references
References 9 publications
0
14
0
Order By: Relevance
“…It is important to mention here that Bouncer is an SLA-aware implementation of policy-based cloud services admission. In case of distributed concurrent applications, such as block chain systems or multi-parallel processing queue service streaming, heuristic solutions have been proposed in [49][50][51] which provide scalability-related solutions to reduce the gap between the service provider and the clients by using a utility factor. A utility factor in case of cloud services admission may be referred to time (scheduling, response time) and budget (pay as you go service usage policy, etc.).…”
Section: Resultsmentioning
confidence: 99%
“…It is important to mention here that Bouncer is an SLA-aware implementation of policy-based cloud services admission. In case of distributed concurrent applications, such as block chain systems or multi-parallel processing queue service streaming, heuristic solutions have been proposed in [49][50][51] which provide scalability-related solutions to reduce the gap between the service provider and the clients by using a utility factor. A utility factor in case of cloud services admission may be referred to time (scheduling, response time) and budget (pay as you go service usage policy, etc.).…”
Section: Resultsmentioning
confidence: 99%
“…4. In conclusion, to guarantee the versatility and robustness of the architecture, three aspects are important to take into account: (i) scalability, microservices can be scaled individually when running a heavy workload just by replicating them on several containers without and not replicating the others underutilized (maximize the performance with minimal cost) [19], [74]; (ii) communication in a microservice, is important establishing simple communication protocol like http, httprest "request/response" (synchronous protocol) or mqtt "publish/subscribe" (asynchronous protocol), depending on needs [67]; (iii) fine-grained microservices, it is fundamental to decompose each service focused on a specific function and of limited influence, according to the established requirements [75]; otherwise, this architecture suffers from a high level of abstraction and coordination among the teams [67], [76].…”
Section: Discussionmentioning
confidence: 99%
“…The framework supports a mix of public, private, and community clouds and provides flexibility at the application level, regardless of the underlying cloud. This includes automated deployment and optimized run‐time orchestration with features such as automated scaling 19 and enhanced security.…”
Section: Micadomentioning
confidence: 99%