DevOpSlang – Bridging the Gap between Development and Operations

Wettinger, Johannes; Breitenbücher, Uwe; Leymann, Frank

doi:10.1007/978-3-662-44879-3_8

Cited by 39 publications

(24 citation statements)

References 6 publications

(7 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Also, it is claimed that adopting DevOps reduces the time to market, as it helps to achieve improved deployment frequency. () (CB04) Scalability. Virmani claims that the use of IaaC (infrastructure as a code) in DevOps ensures that the entire automation is scalable. (CB05) Portability.…”

Section: Resultsmentioning

confidence: 99%

“…DevOps enables to be responsive. () Wettinger et al() consider DevOps as a paradigm that can tightly integrate developers and operators to continuously deliver new iterations of a specific application that makes it possible to meet the expectation of fast feedback to problems and requests. (CB09) Less failure rate. Park et al mention that DevOps is a response to the interdependence of development and operations.…”

Section: Resultsmentioning

confidence: 99%

See 1 more Smart Citation

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

Section: Resultsmentioning

confidence: 99%

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

show abstract

“…Because TOSCA is an emerging standard and tooling support is improving as well, we decided to use TOSCA as an interoperable, intermediate meta model. Further orchestration approaches are originating in the DevOps community such as Amazon OpsWorks [34], Terraform 21 , and DevOpSlang [35]. These can be utilized to orchestrate the transformed artifacts in a more seamless and interoperable manner.…”

Section: Related Workmentioning

confidence: 99%

Standards-Based DevOps Automation and Integration Using TOSCA

Wettinger

Breitenbücher²,

Leymann

2014

2014 IEEE/ACM 7th International Conference on Utility and Cloud Computing

Self Cite

View full text Add to dashboard Cite

“…Thorough and holistic automation is required to enable frequent and continuous software delivery [1]. DevOps is an emerging paradigm [2]- [4] to eliminate the split and barrier between developers and operations personnel:…”

Section: Introduction and Problem Statementmentioning

confidence: 99%

“…Alternatively or additionally, Docker container images can be built to package certain components in an isolated and reusable manner. There are further DevOps tools and corresponding artifacts such as Juju 3 with Juju charms 4 and Puppet [8], [9] with Puppet modules 5 that can be used alternatively or complementary.…”

Section: Introduction and Problem Statementmentioning

confidence: 99%