Key Developer Roles and Organizational Coupling in Microservices: A Longitudinal Analysis
Xiaozhou Li, Nariman Mani, Jose Sosa Rodriguez, Tomas Cerny
TLDR
This study finds that developer roles, particularly "Connectors," significantly influence organizational coupling in microservices, suggesting it's role-driven.
Key contributions
- Analyzes how developer roles (Jacks, Mavens, Connectors) influence organizational coupling (OC) in microservices.
- Longitudinal GitHub data analysis quantifies OC evolution based on commits, issues, and PRs.
- "Connectors" (organizational bridges) are consistently associated with higher organizational coupling.
- Co-occurrence of multiple developer roles within one person further amplifies coupling effects.
Why it matters
This paper shifts the understanding of organizational coupling in microservices from a purely structural issue to a role-driven phenomenon. It offers insights for designing role-aware organizations and developing targeted strategies to manage and decouple microservice systems more effectively.
Original Abstract
Microservice-based systems impose significant organizational coordination challenges, yet the role of individual developers in shaping organizational coupling (OC) remains underexplored. Prior work largely focuses on structural architectural aspects, leaving gaps in understanding how developer roles influence coordination dynamics over time. This study investigates how different developer roles contribute to OC in a large-scale microservices system. The analysis focuses on three key roles, namely Jacks, representing broad knowledge holders, Mavens, representing deep specialists, and Connectors, representing organizational bridges. A longitudinal repository mining analysis of GitHub data, including commits and issue and pull request interactions, is conducted to operationalize OC and quantify its evolution over time. The results show that Connectors are consistently associated with higher levels of OC, while the co-occurrence of multiple roles within the same developer further amplifies coupling effects. In contrast, Jacks and Mavens exhibit more localized and role-specific influences. These findings indicate that OC in microservices is primarily a role-driven phenomenon rather than an inevitable structural property, providing a foundation for role-aware organizational design and targeted decoupling strategies.
📬 Weekly AI Paper Digest
Get the top 10 AI/ML arXiv papers from the week — summarized, scored, and delivered to your inbox every Monday.