Non-Stop Non-Breakable Code Review Services in a Distributed System: Detecting Issues in Real Time

02/11/2022
by   Geunsik Lim, et al.
0

The two most significant bottlenecks in code merging are the build process and the unit tests. However, as the number of items to be checked in a code review increases, that code review becomes a bottleneck for code merging as well. Because of the dependency structure between code review services, an error in one service affects the entire service. As a result, whenever a service error occurs, it is crucial to have methods for determining which code review service has ultimately caused the error. With the goal of achieving a non-stop non-breakable code review service, this paper describes an early error detection method along with a case study of the service.

READ FULL TEXT

page 2

page 3

research
03/14/2018

What Should You Know Before Developing a Service Identification Approach

In this paper, we answer a set of research questions that are required t...
research
03/09/2022

Mining Code Review Data to Understand Waiting Times Between Acceptance and Merging: An Empirical Analysis

Increasing code velocity (or the speed with which code changes are revie...
research
04/19/2020

Code Review in the Classroom

This paper presents a case study to examine the affinity of the code rev...
research
09/04/2023

From Kubernetes to Knactor: A State-Centric Rethink of Service Integration

Microservices are increasingly used in modern applications, leading to a...
research
05/20/2023

Application of Text Analytics in Public Service Co-Creation: Literature Review and Research Framework

The public sector faces several challenges, such as a number of external...
research
05/09/2023

How is the speed of code review affected by activity, usage and code quality?

This paper investigates how the speed of code review is affected by the ...

Please sign up or login with your details

Forgot password? Click here to reset