2014 IEEE 6th International Conference on Cloud Computing Technology and Science 2014
DOI: 10.1109/cloudcom.2014.170
|View full text |Cite
|
Sign up to set email alerts
|

SRL: A Scalability Rule Language for Multi-cloud Environments

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
26
0

Year Published

2016
2016
2020
2020

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 36 publications
(26 citation statements)
references
References 1 publication
0
26
0
Order By: Relevance
“…Also, it is assumed that the deployed service is scalable by design. In [29], a language for scalability rules for multi-cloud environments is proposed as a part of Cloud Application Modeling and Execution Language (CAMEL). It provides high expressiveness in terms of event patterns, performance metrics and scaling actions, at the cost of a complex form.…”
Section: State Of the Artmentioning
confidence: 99%
“…Also, it is assumed that the deployed service is scalable by design. In [29], a language for scalability rules for multi-cloud environments is proposed as a part of Cloud Application Modeling and Execution Language (CAMEL). It provides high expressiveness in terms of event patterns, performance metrics and scaling actions, at the cost of a complex form.…”
Section: State Of the Artmentioning
confidence: 99%
“…A DSL language, named Scalability Rule Language (SRL), has been proposed in [Kritikos 2014] for specifying scalability rules through defining event patterns of multi-Cloud application as well as scaling actions. SRL has been inspired by OWL-Q language for specifying QoS metrics as well as the Esper Processing Language (EPL) for specifying event patterns.…”
Section: Elasticity Strategies Descriptionmentioning
confidence: 99%
“…• Granularity : Even though some of the studied approaches , Copil 2013, Kritikos 2014 have tried specifying QoS requirements (e.g, the defined thresholds for QoS metrics) at different granularity levels, none of them have considered the request level, i.e., distinguishing between requests requirements. In fact, all of them have assumed that QoS related requirements are the same for all requests.…”
Section: Synthesis Of Related Workmentioning
confidence: 99%
“…Enhancing the role of the cloud broker as guarantor of quality assurance was the premise behind the EU FP7 BrokerCloud project , which investigated methods and mechanisms for continuous quality assurance and optimization of brokered software services in the cloud. The project demonstrated a brokerage platform which could validate and test software services prior to uploading ( certification at onboarding ) , manage the service lifecycle from creation to decommissioning ( lifecycle governance ) , regulate the performance and availability of services ( monitoring and adaptation ) and recommend alternative service bundles, according to customer preferences ( preference‐based arbitrage ) . The current article describes the novel verification and testing approach that was developed to assure functional quality and substitutability, as part of a service certification strategy.…”
Section: Introductionmentioning
confidence: 99%