Key Developer Roles and Organizational Coupling in Microservices: A Longitudinal Analysis

TL;DR

This longitudinal study analyzes how developer roles like Jacks, Mavens, and Connectors influence organizational coupling in microservices, revealing role-driven effects on system coordination over time.

Contribution

It identifies the specific impacts of different developer roles on organizational coupling, emphasizing role-driven dynamics in microservice coordination.

Findings

Connectors are linked to higher organizational coupling.

Multiple roles within a developer amplify coupling effects.

Jacks and Mavens have more localized influence.

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.