%0 Report %1 SPEC-RG-2015-001-DevOpsPerformanceResearchAgenda %A Brunnert, Andreas %A van Hoorn, Andre %A Willnecker, Felix %A Danciu, Alexandru %A Hasselbring, Wilhelm %A Heger, Christoph %A Herbst, Nikolas %A Jamshidi, Pooyan %A Jung, Reiner %A von Kistowski, Joakim %A Koziolek, Anne %A Kroß, Johannes %A Spinner, Simon %A Vögele, Christian %A Walter, Jürgen %A Wert, Alexander %D 2015 %K imported %N SPEC-RG-2015-01 %T Performance-oriented DevOps: A Research Agenda %U http://research.spec.org/fileadmin/user_upload/documents/wg_rgdevops/endorsed_publications/SPEC-RG-2015-001-DevOpsPerformanceResearchAgenda.pdf %X DevOps is a trend towards a tighter integration between development (Dev) and operations (Ops) teams. The need for such an integration is driven by the requirement to continuously adapt enterprise applications (EAs) to changes in the business environment. As of today, DevOps concepts have been primarily introduced to ensure a constant flow of features and bug fixes into new releases from a functional perspective. In order to integrate a non-functional perspective into these DevOps concepts this report focuses on tools, activities, and processes to ensure one of the most important quality attributes of a software system, namely performance. Performance describes system properties concerning its timeliness and use of resources. Common metrics are response time, throughput, and resource utilization. Performance goals for EAs are typically defined by setting upper and/or lower bounds for these metrics and specific business transactions. In order to ensure that such performance goals can be met, several activities are required during development and operation of these systems as well as during the transition fromDev to Ops. Activities during development are typically summarized by the term Software Performance Engineering (SPE), whereas activities during operations are called Application Performance Management (APM). SPE and APM were historically tackled independently from each other, but the newly emerging DevOps concepts require and enable a tighter integration between both activity streams. This report presents existing solutions to support this integration as well as open research challenges in this area. The report starts by defining EAs and summarizes their characteristics that make performance evaluations for these systems particularly challenging. It continues by describing our understanding of DevOps and explaining the roots of this trend to set the context for the remaining parts of the report. Afterwards, performance management activities that are common in both life cycle phases are explained, until the particularities of SPE and APM are discussed in separate sections. Finally, the report concludes by outlining activities and challenges to support the rapid iteration between Dev and Ops.

@techreport{SPEC-RG-2015-001-DevOpsPerformanceResearchAgenda, abstract = {DevOps is a trend towards a tighter integration between development (Dev) and operations (Ops) teams. The need for such an integration is driven by the requirement to continuously adapt enterprise applications (EAs) to changes in the business environment. As of today, DevOps concepts have been primarily introduced to ensure a constant flow of features and bug fixes into new releases from a functional perspective. In order to integrate a non-functional perspective into these DevOps concepts this report focuses on tools, activities, and processes to ensure one of the most important quality attributes of a software system, namely performance. Performance describes system properties concerning its timeliness and use of resources. Common metrics are response time, throughput, and resource utilization. Performance goals for EAs are typically defined by setting upper and/or lower bounds for these metrics and specific business transactions. In order to ensure that such performance goals can be met, several activities are required during development and operation of these systems as well as during the transition fromDev to Ops. Activities during development are typically summarized by the term Software Performance Engineering (SPE), whereas activities during operations are called Application Performance Management (APM). SPE and APM were historically tackled independently from each other, but the newly emerging DevOps concepts require and enable a tighter integration between both activity streams. This report presents existing solutions to support this integration as well as open research challenges in this area. The report starts by defining EAs and summarizes their characteristics that make performance evaluations for these systems particularly challenging. It continues by describing our understanding of DevOps and explaining the roots of this trend to set the context for the remaining parts of the report. Afterwards, performance management activities that are common in both life cycle phases are explained, until the particularities of SPE and APM are discussed in separate sections. Finally, the report concludes by outlining activities and challenges to support the rapid iteration between Dev and Ops.}, added-at = {2018-02-14T17:55:46.000+0100}, author = {Brunnert, Andreas and van Hoorn, Andre and Willnecker, Felix and Danciu, Alexandru and Hasselbring, Wilhelm and Heger, Christoph and Herbst, Nikolas and Jamshidi, Pooyan and Jung, Reiner and von Kistowski, Joakim and Koziolek, Anne and Kro{\ss}, Johannes and Spinner, Simon and V{\"o}gele, Christian and Walter, J{\"u}rgen and Wert, Alexander}, biburl = {https://puma.ub.uni-stuttgart.de/bibtex/2635e8d445695646feca7914f0bb1e66a/andrevanhoorn}, file = {SPEC-RG-2015-001-DevOpsPerformanceResearchAgenda.pdf:avanhoorn/SPEC-RG-2015-001-DevOpsPerformanceResearchAgenda.pdf:PDF}, institution = {SPEC Research Group --- DevOps Performance Working Group, Standard Performance Evaluation Corporation (SPEC)}, interhash = {e103e346585287c2f11d51efad84d6cc}, intrahash = {635e8d445695646feca7914f0bb1e66a}, keywords = {imported}, month = aug, number = {SPEC-RG-2015-01}, timestamp = {2020-02-27T22:31:36.000+0100}, title = {Performance-oriented {DevOps}: {A} Research Agenda}, url = {http://research.spec.org/fileadmin/user_upload/documents/wg_rgdevops/endorsed_publications/SPEC-RG-2015-001-DevOpsPerformanceResearchAgenda.pdf}, year = 2015 }