Due to its enormous benefits, the research and industry communities have shown an increasing interest in the Microservices Architecture (MSA) style over the last few years. Despite this, there is a limited evidence-based and thorough understanding of the types of issues (e.g., faults, errors, failures, mistakes) faced by microservices system developers and causes that trigger the issues. Such evidence-based understanding of issues and causes is vital for long-term, impactful, and quality research and practice in the MSA style. To that end, we conducted an empirical study on 1,345 issue discussions extracted from five open source microservices systems hosted on GitHub. Our analysis led to the first of its kind taxonomy of the types of issues in open source microservices systems, informing that the problems originating from Technical debt (321, 23.86%), Build (145, 10.78%), Security (137, 10.18%), and Service execution and communication (119, 8.84%) are prominent. We identified that "General programming errors", "Poor security management", "Invalid configuration and communication", and "Legacy versions, compatibility and dependency" are the predominant causes for the leading four issue categories. Study results streamline a taxonomy of issues, their mapping with underlying causes, and present empirical findings that could facilitate research and development on emerging and next-generation microservices systems.
Understanding the Issues, Their Causes and Solutions in Microservices Systems: An Empirical Study
Tampere University(坦佩雷大学);Wuhan University(武汉大学);University of Derby(德比大学);University of Oulu(奥卢大学);RMIT University(皇家墨尔本理工大学);University of Jyväskylä(于韦斯屈莱大学)
Anomaly Detection and Root Cause Analysis for Microservice Systems
Viet Nam National University Ho Chi Minh City - University of Technology (HCMUT)(越南国家大学胡志明城-技术大学(HCMUT));School of Computing Technologies(计算技术学院);College of Science, Technology, Engineering and Maths(科学、技术、工程和数学学院);Royal Melbourne Institute of Technology (RMIT University)(皇家墨尔本理工学院(RMIT大学))
Intertwining Ecosystems: A Large Scale Empirical Study of Libraries that Cross Software Ecosystems
各种技术栈和第三方库使用的增加导致开发人员不可避免地切换技术。为了帮助这些开发人员,维护人员已经开始将他们的库发布到多种技术,即,一个跨生态系统的图书馆我们的目标是探索这些跨生态系统库在生态系统之间交织的程度。我们对来自五个不同软件生态系统的110万个库进行了大规模的实证研究,即,PyPI for Python,CRAN for R,Maven for Java,RubyGems for Ruby,NPM for JavaScript,以确定4,146个GitHub项目,这些项目将库发布到这五个生态系统。分析他们的贡献,我们首先发现这些跨生态系统库的绝大多数贡献者(中位数为37.5%)来自单一生态系统,同时也从目标生态系统之外获得了很大一部分贡献(中位数为24.06%)。我们还发现,跨生态系统库是使用多种程序设计语言编写的。具体而言,三个(即,PyPI,CRAN,RubyGems)的大部分源代码都是使用非特定于该生态系统的语言编写的。随着生态系统变得相互交织,这为研究开辟了新的途径,例如跨生态系统库是否可以解决寻找替代库的问题,或者这些库如何适应每个生态系统。
Reflections on the Reproducibility of Commercial LLM Performance in Empirical Software Engineering Studies
fortiss and Blekinge Institute of Technology(fortiss 和 莱比锡技术学院);University of the Bundeswehr Munich(联邦国防军大学穆尔海姆分校);Blekinge Institute of Technology(莱比锡技术学院);Technical University of Munich(慕尼黑技术大学)