Towards Architecting for Continuous Delivery

Chen, Lianping

doi:10.1109/wicsa.2015.23

Cited by 30 publications

(41 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The study [32] argues that some of these factors (e.g., work breakdown) can be limited by the architecture of a system. Chen [22] reports on the experience of architecting 25 software applications for continuous delivery. The study indicates that continuous delivery creates new challenges for architecting software applications.…”

Section: Architecting For CI and Cd Practicesmentioning

confidence: 99%

“…The findings from our interviews indicated that deployability has gained a high priority in CD as the interviewees frequently shared that deployability concerns are accredited during architectural design and drive many decisions to have independently deployable units [2,22]. We were interested in understanding how deployability concerns impact different aspects of (architecture) design.…”

Section: Deployabilitymentioning

confidence: 99%

“…Building and delivering an application on a continuous basis may potentially increase the number of errors, and the chance of unavailability of the application [1,22]. This compelled the participants' organizations to have more investment in logging (i.e., the process of recording a time series of events of a system at runtime [1]) and monitoring (i.e., the process of checking the state of a system) in order to hypothesize and run experiments for examining different functionalities of a system, identify and resolve performance issues, and recover the application in case of problems.…”

Section: Loggability and Monitorabilitymentioning

confidence: 99%

“…It has recently been claimed that the fundamental limitations to adopting CD practices are deeply ingrained in the architecture of a system and these practices may bring substantial architectural implications [1,2,18,19]. Whilst the industrial community, through white papers and practitioners' blogs, has investigated the role of software architecture in CD adoption [2, 20,21], there is little empirical effort to study how software architecture is being impacted by or is impacting CD practices [22][23][24]. This is evident in the recently published systematic reviews on CD [18,19,25], in which a new line of research has been called to explore how an application should be (re-) architected for CD.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

An empirical study of architecting for continuous delivery and deployment

et al. 2018

View full text Add to dashboard Cite

Recently, many software organizations have been adopting Continuous Delivery and Continuous Deployment (CD) practices to develop and deliver quality software more frequently and reliably. Whilst an increasing amount of the literature covers different aspects of CD, little is known about the role of software architecture in CD and how an application should be (re-) architected to enable and support CD. We have conducted a mixed-methods empirical study that collected data through indepth, semi-structured interviews with 21 industrial practitioners from 19 organizations, and a survey of 91 professional software practitioners. Based on a systematic and rigorous analysis of the gathered qualitative and quantitative data, we present a conceptual framework to support the process of (re-) architecting for CD. We provide evidence-based insights about practicing CD within monolithic systems and characterize the principle of "small and independent deployment units" as an alternative to the monoliths. Our framework supplements the architecting process in a CD context through introducing the quality attributes (e.g., resilience) that require more attention and demonstrating the strategies (e.g., prioritizing operations concerns) to design operations-friendly architectures. We discuss the key insights (e.g., monoliths and CD are not intrinsically oxymoronic) gained from our study and draw implications for research and practice.

show abstract

Section: Architecting For CI and Cd Practicesmentioning

confidence: 99%

Section: Deployabilitymentioning

confidence: 99%

Section: Loggability and Monitorabilitymentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

An empirical study of architecting for continuous delivery and deployment

et al. 2018

View full text Add to dashboard Cite

show abstract

“…Advancements in Continuous Integration and Continuous Deployment enable companies to quickly build enhanced versions and variants of their products and deploy them to their customers over the Internet. The ability to communicate with the product in the field, however, provides an unprecedented opportunity that enables software companies not only to deploy, but also to collect data (for example, product logs).…”

Section: Introductionmentioning

confidence: 99%

Experimentation growth: Evolving trustworthy A/B testing capabilities in online software companies

Fabijan

Dmitriev²,

McFarland³

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

Companies need to know how much value their ideas deliver to customers. One of the most powerful ways to accurately measure this is by conducting online controlled experiments (OCEs). To run experiments, however, companies need to develop strong experimentation practices as well as align their organization and culture to experimentation. The main objective of this paper is to demonstrate how to run OCEs at large scale using the experience of companies that succeeded in scaling. Based on case study research at Microsoft, Booking.com, Skyscanner, and Intuit, we present our main contribution—The Experiment Growth Model. This four‐stage model addresses the seven critical aspects of experimentation and can help companies to transform their organizations into learning laboratories where new ideas can be tested with scientific accuracy. Ultimately, this should lead to better products and services.

show abstract

A qualitative study of architectural design issues in DevOps

Shahin

Nasab

Babar

2021

J Software Evolu Process

View full text Add to dashboard Cite

Software architecture is critical in succeeding with Development and Operations (DevOps). However, designing software architectures that enable and support DevOps (DevOps‐driven software architectures) is a challenge for organizations. We assert that one of the essential steps towards characterizing DevOps‐driven architectures is to understand architectural design issues raised in DevOps. At the same time, some of the architectural issues that emerge in the DevOps context (and their corresponding architectural practices or tactics) may stem from the context (i.e., domain) and characteristics of software organizations. To this end, we conducted a mixed‐methods study that consists of a qualitative case study of two teams in a company during their DevOps transformation and a content analysis of Stack Overflow and DevOps Stack Exchange posts to understand architectural design issues in DevOps. Our study found eight specific and contextual architectural design issues faced by the two teams and classified architectural design issues discussed in Stack Overflow and DevOps Stack Exchange into 11 groups. Our aggregated results reveal that the main characteristics of DevOps‐driven architectures are being loosely coupled and prioritizing deployability, testability, supportability, and modifiability over other quality attributes. Finally, we discuss some concrete implications for research and practice.

show abstract

Towards Architecting for Continuous Delivery

Cited by 30 publications

References 3 publications

An empirical study of architecting for continuous delivery and deployment

An empirical study of architecting for continuous delivery and deployment

Experimentation growth: Evolving trustworthy A/B testing capabilities in online software companies

A qualitative study of architectural design issues in DevOps

Contact Info

Product

Resources

About