Toward Organizational Decoupling in Microservices Through Key Developer Allocation

Abstract: With microservices continuously being popular in the software architecture domain, more practitioners and researchers have begun to pay attention to the degradation issue that diminishes its sustainability. One of the key factors that causes the degradation of the architecture is that of the software architectural structure according to Conway's law. However, the best practice of "One microservice per Team", advocated widely by the industry, is not commonly adopted, especially when many developers contribute heavily across multiple microservices and create organizational coupling. Therein, many key developers, who are responsible for the majority of the project work and irreplaceable to the team, can also create the most coupling and be the primary cause of microservice degradation. Hence, to properly maintain microservice architecture in terms of its organizational structure, we shall identify these key developers and understand their connections to the organizational coupling within the project. We propose an approach to identify the key developers in microservice projects and investigate their connection to organizational coupling. The approach shall facilitate the maintenance and optimization of microservice projects against degradation by detecting and mitigating organizational coupling.

• The paper introduces a novel methodology using artifact traceability graphs and metrics like file coverage ratio and betweenness centrality to identify key developers.
• The paper quantifies how developer contribution switches drive organizational coupling, which in turn contributes to architectural decay in microservices.
• The paper proposes decoupling strategies that balance key developer influence with improved resource allocation to sustain microservice architecture.

Toward Organizational Decoupling in Microservices Through Key Developer Allocation

Introduction

The architectural degradation of microservices due to organizational coupling represents a critical sustainability issue. Leveraging Conway's Law, this research scrutinizes the often-neglected misalignment between architectural and organizational structures. Despite the ideal of "One microservice per team," organizational coupling persists, predominantly driven by key developers. These developers, though vital, inadvertently introduce coupling, prompting architectural decay. This paper proposes an approach to identify such influencers and investigates their effect on the organizational coupling within microservice projects to facilitate more sustainable project management and architecture.

Key Developer Identification

This study employs a methodical approach utilizing artifact traceability graphs to identify Jack, Maven, and Connector developers across microservices. Jack developers possess broad project knowledge, Maven developers exhibit mastery over specific modules, and Connector developers facilitate inter-project collaboration. By calculating metrics such as file coverage ratio and betweenness centrality, the identified key developers demonstrate a disproportionate impact on multiple microservices, frequently occupying several roles simultaneously. Notably, their influence often transitions across project phases as developer dynamics evolve over time.

Organizational Coupling Evaluation

The paper explores the evaluation of organizational coupling by determining the frequency of developer transitions between microservices, termed as contribution switches. Coupling evaluation utilizes a developer's average contributions across services, weighted by contribution switch frequency, to quantify organizational coupling introduced by key developers. The data indicates a marked reduction in organizational coupling over time, reflecting improved organizational structuring, while revealing that key developers contribute substantially to this coupling.

Discussion and Implications

The findings confirm that key developers are the primary agents of organizational coupling, thus precipitating architectural degradation. This realization paves the way for an organizational decoupling approach to optimize resource allocation and minimize coupling. Future research should expand upon this groundwork to refine decoupling strategies, explore dynamic monitoring of architectural health, and enhance the integration of developer profiles in organizational decisions. Applying motivations and generative AI tools will further evolve the practical implementations of these insights in software development environments.

Conclusion

The paper establishes a method for leveraging key developer identification to understand and address organizational coupling in microservice architectures. Ultimately, the study aids in developing a technical framework conducive to sustainable microservice management, highlighting the necessity to balance developer expertise with organizational demands to mitigate long-term architectural degradation. This work underlines the importance of maintaining a refined alignment between microservices' organizational and architectural structures to sustain project viability and progression.