CloudWave: Where adaptive cloud management meets DevOps

Bruneo, Dario; Fritz, Thomas; Keidar-Barner, Sharon; Leitner, Philipp; Longo, Francesco; Marquezan, Clarissa Cassales; Metzger, Andreas; Pohl, Klaus; Puliafito, Antonio; Raz, Danny; Röth, Andreas; Salant, Eliot; Segall, Itai; Villari, Massimo; Wolfsthal, Yaron; Woods, Chris

doi:10.1109/iscc.2014.6912638

Cited by 31 publications

(14 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This establishes a connection to research to Feedback-Driven Development [4,8]. However, it is crucial to note that the use of the proposed CostHat model is not limited to pre-deployment tooling.…”

Section: Related Workmentioning

confidence: 70%

Modelling and managing deployment costs of microservice-based cloud applications

Leitner

Cito

Stöckli

2016

Proceedings of the 9th International Conference on Utility and Cloud Computing

Self Cite

View full text Add to dashboard Cite

We present an approach to model the deployment costs, including compute and IO costs, of Microservice-based applications deployed to a public cloud. Our model, which we dubbed CostHat, supports both, Microservices deployed on traditional IaaS or PaaS clouds, and services that make use of novel cloud programming paradigms, such as AWS Lambda. CostHat is based on a network model, and allows for what-if and cost sensitivity analysis. Further, we have used this model to implement tooling that warns cloud developers directly in the Integrated Development Environment (IDE) about certain classes of potentially costly code changes. We illustrate our work based on a case study, and evaluate the CostHat model using a standalone Python implementation. We show that, once instantiated, cost calculation in CostHat is computationally inexpensive on standard hardware (below 1 ms even for applications consisting of thousand services and endpoints). This enables its use in real-time for developer tooling which continually re-evaluates the costs of an application in the background, while the developer is working on the code.

show abstract

Section: Related Workmentioning

confidence: 70%

Modelling and managing deployment costs of microservice-based cloud applications

Leitner

Cito

Stöckli

2016

Proceedings of the 9th International Conference on Utility and Cloud Computing

Self Cite

View full text Add to dashboard Cite

show abstract

“…DevOps speeds up the processes from development to operation. () Bruneo et al say DevOps can promote collaboration between developers and operational teams that leads to shortening the loop between software development, deployment, and operation. (CB14) Flexible software development. DevOps enables development and operations teams to be more flexible by providing close collaboration in implementing customer requirements.…”

Section: Resultsmentioning

confidence: 99%

Towards a benefits dependency network for DevOps based on a systematic literature review

Jabbari

Ali

Petersen

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

DevOps as a new way of thinking for software development and operations has received much attention in the industry, while it has not been thoroughly investigated in academia yet. The objective of this study is to characterize DevOps by exploring its central components in terms of principles, practices and their relations to the principles, challenges of DevOps adoption, and benefits reported in the peer-reviewed literature. As a key objective, we also aim to realize the relations between DevOps practices and benefits in a systematic manner. A systematic literature review was conducted. Also, we used the concept of benefits dependency network to synthesize the findings, in particular, to specify dependencies between DevOps practices and link the practices to benefits. We found that in many cases, DevOps characteristics, ie, principles, practices, benefits, and challenges, were not sufficiently defined in detail in the peer-reviewed literature.In addition, only a few empirical studies are available, which can be attributed to the nascency of DevOps research. Also, an initial version of the DevOps benefits dependency network has been derived. The definition of DevOps principles and practices should be emphasized given the novelty of the concept. Further empirical studies are needed to improve the benefits dependency network presented in this study. KEYWORDSbenefits and values, challenges, development and operations, DevOps, principles and practices, systematic literature review

show abstract

“…The most authoritive source on this is [26], albeit not an academic study per se. Other related works in this field include our own previous work [9] and the work conducted in the CloudWave project [7].…”

Section: Related Workmentioning

confidence: 99%

An empirical study on principles and practices of continuous delivery and deployment

Schermann

Cito

Leitner

et al. 2016

Preprint

Self Cite

View full text Add to dashboard Cite

Despite substantial recent research activity related to continuous delivery and deployment (CD), there has not yet been a systematic, empirical study on how the practices often associated with continuous deployment have found their way into the broader software industry. This raises the question to what extent our knowledge of the area is dominated by the peculiarities of a small number of industrial leaders, such as Facebook. To address this issue, we conducted a mixed-method empirical study, consisting of a pre-study on literature, qualitative interviews with 20 software developers or release engineers with heterogeneous backgrounds, and a Web-based quantitative survey that attracted 187 complete responses. A major trend in the results of our study is that architectural issues are currently one of the main barriers for CD adoption. Further, feature toggles as an implementation technique for partial rollouts lead to unwanted complexity, and require research on better abstractions and modelling techniques for runtime variability. Finally, we conclude that practitioners are in need for more principled approaches to release decision making, e.g., which features to conduct A/B tests on, or which metrics to evaluate.

show abstract

CloudWave: Where adaptive cloud management meets DevOps

Cited by 31 publications

References 18 publications

Modelling and managing deployment costs of microservice-based cloud applications

Modelling and managing deployment costs of microservice-based cloud applications

Towards a benefits dependency network for DevOps based on a systematic literature review

An empirical study on principles and practices of continuous delivery and deployment

Contact Info

Product

Resources

About