Change impact analysis in microservice systems: A systematic literature

Background: Change impact analysis is crucial in software development, especially when working with large and complex systems. It aims to identify the potential consequences of a change or estimate what needs to be modified to accomplish a change. The importance of such an analysis multiplies in decentralized environments. Microservice systems are decentralized and represent the current industry mainstream for scalable systems. Objective: While individual microservices intend to be self-contained and independent, certain overlap with other microservices is inevitable since they interact. In the context of microservice systems, changes in one microservice can affect other microservices without a direct connection, leading to ripple effects and extended maintenance efforts. To understand the current state of the art for microservices with respect to the change impact analysis, the objective of this work is to study and analyze existing literature to summarize the evidence and to provide readers with a roadmap to established approaches. Methods: We conduct a systematic literature review targeting studies related to change impact analysis in microservices. The study considered 1,669 papers and filtered them down to 29 works included in this study. Results: This manuscript introduces different types of change impacts introduced in the literature. It compares and categorizes tools and methods that have been used in literature to measure the impact of change in microservices. It illustrates what units of measure have been used. Finally, it shares system benchmarks used to assess change impact analysis methods. Open Challenges. A number of open challenges and gaps are found in the tools and methods. These challenges are related to the improvement of the detection techniques, additional impact analysis, and validation of approaches. Many of the solutions measure a specific aspect of an impacted system, without taking into account multiple effects. Impact analysis is seen as measured indirectly by these solutions as well, and more direct observation is needed. Conclusion: The results provide a reference to microservice developers and quality engineers to maintain better-quality systems. With a roadmap to the topic, our researcher peers might easily understand various directions that have been approached on this topic. Finally, this work serves as a reference for development-aiding tools helping to manage microservice system evolution.