The reviewed record of science sign in
Pith

arxiv: 2606.16725 · v2 · pith:X3HP5OUG · submitted 2026-06-15 · cs.SE

Organizational Cohesion in Microservice Architectures: A Multi-Project Empirical Study

Xiaozhou Li , Andrea Janes This is my paper

Reviewed by Pith T0 review T1 audit T2 compute T3 formal T4 kernel 2026-06-27 03:44 UTCgrok-4.3pith:X3HP5OUGrecord.jsonopen to challenge →

classification cs.SE
keywords organizational cohesionmicroservice architecturespairwise team cohesiondeveloper contributionssocio-technical alignmentservice couplingempirical study
0
0 comments X

The pith

Pairwise Team Cohesion and Average Organizational Coupling correlate only weakly across seven microservice projects.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The paper defines organizational cohesion as the balance of developer contributions inside individual microservices. It adapts the Sensitive Class Cohesion Metric into Pairwise Team Cohesion (PTC) and applies the measure to the Spinnaker platform plus six additional open-source microservice systems. The analysis finds systematic differences between core and peripheral services. PTC shows only weak correlation with Average Organizational Coupling (AOC), indicating that internal team focus and cross-service developer activity represent separate organizational patterns. This extends the high-cohesion low-coupling principle from code structure to the people who maintain the services.

Core claim

By adapting SCOM, the study measures Pairwise Team Cohesion (PTC) as the balance and focus of developer contributions within microservices. Longitudinal analysis of Spinnaker and replication across six other projects reveal that PTC and Average Organizational Coupling (AOC) exhibit only a weak correlation across projects. This finding shows that team cohesion and cross-service developer activity suggest distinct and weakly associated organizational dynamics.

What carries the argument

Pairwise Team Cohesion (PTC), which quantifies the concentration of developer effort within each microservice by adapting the Sensitive Class Cohesion Metric (SCOM) to contribution counts.

If this is right

  • Core services display different cohesion patterns from peripheral services.
  • Team cohesion inside services and cross-service coupling can be tracked as independent metrics.
  • The high-cohesion low-coupling principle extends directly to the organizational level.
  • Microservice boundaries should be evaluated against both technical and contributor-activity factors.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • Teams could monitor PTC separately to detect when internal focus drifts from service boundaries.
  • Similar contribution-based cohesion measures might apply to modular systems outside microservices.
  • Adjusting team assignments to raise PTC could be tested for effects on service evolution speed.

Load-bearing premise

Adapting the Sensitive Class Cohesion Metric to developer contribution counts inside microservices produces a meaningful measure of organizational cohesion.

What would settle it

A strong positive correlation between PTC and AOC in additional microservice projects would challenge the claim of only weak association.

Figures

Figures reproduced from arXiv: 2606.16725 by Andrea Janes, Xiaozhou Li.

Figure 1
Figure 1. Figure 1: Evolution of organizational cohesion (PTC) and coupling (AOC) for 12 [PITH_FULL_IMAGE:figures/full_fig_p009_1.png] view at source ↗
Figure 2
Figure 2. Figure 2: Distribution of organizational cohesion (PTC) and coupling (AOC) across [PITH_FULL_IMAGE:figures/full_fig_p010_2.png] view at source ↗
Figure 3
Figure 3. Figure 3: PTC vs AOC across all projects substantially; 2) Microservice systems exhibit diverse organizational structures, ranging from tightly coupled to highly decoupled ecosystems; 3) The relationship between cohesion and coupling is consistently weak across projects. These results suggest that cohesion and coupling should be analyzed as sep￾arate organizational dimensions rather than as opposite ends of a single… view at source ↗
read the original abstract

The widespread adoption of microservice architectures has introduced new challenges in aligning software modularity with the structure of development organizations. Although prior research has extensively examined technical properties such as service coupling and dependency structures, comparatively little attention has been paid to how contributor activity reflects or diverges from service boundaries. In this paper, we introduce the notion of organizational cohesion in microservice ecosystems and propose a quantitative approach to measure it. Building on the Sensitive Class Cohesion Metric (SCOM), we define Pairwise Team Cohesion (PTC), a metric that captures the balance and focus of developer contributions within individual microservices. We analyze the evolution of organizational cohesion using a longitudinal case study of the Spinnaker microservice platform and replicate the analysis across six additional open-source microservice systems. Our results reveal systematic differences between core and peripheral services and show that PTC and Average Organizational Coupling (AOC) exhibit only a weak correlation across projects. This finding shows that team cohesion and cross-service developer activity suggest distinct and weakly associated organizational dynamics. By extending the "high cohesion, low coupling" principle to the organizational level, our study provides a quantitative perspective for assessing the socio-technical structure of microservice development.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

0 major / 2 minor

Summary. The paper introduces Pairwise Team Cohesion (PTC), an adaptation of the Sensitive Class Cohesion Metric (SCOM) that substitutes developer contribution counts for method/attribute references to quantify organizational cohesion within microservices. Through a longitudinal analysis of the Spinnaker platform and replication across six additional open-source microservice systems, it identifies systematic differences between core and peripheral services and reports only a weak correlation between PTC and Average Organizational Coupling (AOC), concluding that team cohesion and cross-service developer activity represent distinct and weakly associated organizational dynamics. This extends the high-cohesion low-coupling principle to the socio-technical level.

Significance. If the reported weak correlation holds under the provided dataset and adaptation, the work supplies a useful quantitative metric for assessing socio-technical congruence in microservice architectures. The multi-project empirical design with longitudinal tracking and the direct, parameter-free substitution in the PTC definition are strengths that support generalizability and falsifiability. The finding that PTC and AOC are only weakly associated offers a concrete basis for distinguishing intra-service team focus from inter-service activity patterns.

minor comments (2)
  1. [Abstract] Abstract: the adaptation of SCOM is described only at a high level; adding one sentence on the direct substitution of contribution counts would make the central metric definition immediately clear without requiring the reader to reach the methods section.
  2. [Results or Methods] The manuscript would benefit from an explicit table (e.g., in §4 or §5) summarizing the seven projects' key attributes (number of services, contributors, observation period, commit volume) to support replication claims and cross-project comparison.

Simulated Author's Rebuttal

0 responses · 0 unresolved

We thank the referee for the constructive review and the recommendation of minor revision. The report provides a clear summary of our contributions and highlights the strengths of the multi-project design and the PTC metric. No specific major comments were listed in the report, so we have no points requiring detailed rebuttal at this stage. We will incorporate any minor suggestions during revision.

Circularity Check

0 steps flagged

No significant circularity detected

full rationale

The paper's central claim is an empirical observation of weak correlation between PTC (defined by explicit adaptation of SCOM via substitution of contribution counts for references) and AOC, computed directly on the seven-project dataset. No equations reduce the reported correlation to a fitted parameter, no self-citation chain bears the load of the result, and the adaptation is presented as a transparent re-use of an external metric rather than a self-referential construction. The derivation chain consists of metric definition, data collection, and statistical computation, all externally verifiable from the supplied formulas and dataset.

Axiom & Free-Parameter Ledger

0 free parameters · 1 axioms · 1 invented entities

The central claim rests on the untested transfer of a code-level cohesion metric to organizational contribution counts and on the representativeness of seven open-source projects.

axioms (1)
  • domain assumption SCOM can be meaningfully repurposed from class-level code cohesion to team-level contribution cohesion inside microservices
    Stated in the abstract as the basis for defining PTC
invented entities (1)
  • Pairwise Team Cohesion (PTC) no independent evidence
    purpose: Quantitative measure of organizational cohesion
    Newly defined metric; no independent evidence outside the study itself

pith-pipeline@v0.9.1-grok · 5737 in / 1165 out tokens · 36853 ms · 2026-06-27T03:44:58.558186+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Reference graph

Works this paper leans on

28 extracted references · 2 canonical work pages · 2 internal anchors

  1. [1]

    ACM Transactions on Software Engineering and Methodology (TOSEM)21(2), 1–34 (2012)

    Al Dallal, J., Briand, L.C.: A precise method-method interaction-based cohesion metric for object-oriented classes. ACM Transactions on Software Engineering and Methodology (TOSEM)21(2), 1–34 (2012)

    2012

  2. [2]

    Amoroso d’Aragona, D., Li, X., Cerny, T., Janes, A., Lenarduzzi, V., Taibi, D.: One microservice per developer: is this the trend in oss? In: European Conference on Service-Oriented and Cloud Computing. pp. 19–34. Springer (2023)

    2023

  3. [3]

    In: Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement

    Cataldo, M., Herbsleb, J.D., Carley, K.M.: Socio-technical congruence: a frame- work for assessing the impact of technical and work dependencies on software development productivity. In: Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement. pp. 2–11 (2008)

    2008

  4. [4]

    In: Conference proceedings on Object-oriented programming systems, languages, and applications

    Chidamber,S.R.,Kemerer,C.F.:Towardsametricssuiteforobjectorienteddesign. In: Conference proceedings on Object-oriented programming systems, languages, and applications. pp. 197–211 (1991)

    1991

  5. [5]

    IEEE Transactions on software engineering20(6), 476–493 (1994)

    Chidamber, S.R., Kemerer, C.F.: A metrics suite for object oriented design. IEEE Transactions on software engineering20(6), 476–493 (1994)

    1994

  6. [6]

    Datamation14(4), 28–31 (1968)

    Conway, M.E.: How do committees invent. Datamation14(4), 28–31 (1968)

    1968

  7. [7]

    ACM Transactions on Software Engineering and Methodology (TOSEM)15(2), 123–149 (2006)

    Counsell, S., Swift, S., Crampton, J.: The interpretation and utility of three cohe- sion metrics for object-oriented design. ACM Transactions on Software Engineering and Methodology (TOSEM)15(2), 123–149 (2006)

    2006

  8. [8]

    Present and ulterior software engineering pp

    Dragoni, N., Giallorenzo, S., Lafuente, A.L., Mazzara, M., Montesi, F., Mustafin, R., Safina, L.: Microservices: yesterday, today, and tomorrow. Present and ulterior software engineering pp. 195–216 (2017)

    2017

  9. [9]

    Information Theories & Applications13, 82–91 (2006)

    Fernández, L., Peña, R.: A sensitive metric of class cohesion. Information Theories & Applications13, 82–91 (2006)

    2006

  10. [10]

    Glover, A.: Spinnaker sets sail to the continu- ous delivery foundation.https://netflixtechblog.com/ spinnaker-sets-sail-to-the-continuous-delivery-foundation-e81cd2cbbfeb (2019), accessed: 2025-10-19 Organizational Cohesion in Microservices 17

    2019

  11. [11]

    Prentice- Hall, Inc

    Henderson-Sellers, B.: Object-oriented metrics: measures of complexity. Prentice- Hall, Inc. (1995)

    1995

  12. [12]

    In: Proceedings of the 21st international conference on Software engineering

    Herbsleb, J.D., Grinter, R.E.: Splitting the organization and integrating the code: Conway’s law revisited. In: Proceedings of the 21st international conference on Software engineering. pp. 85–95 (1999)

    1999

  13. [13]

    the International Symposium on Applied Corporate Computing (1995)

    Hitz, M., Montazeri, B.: Measuring coupling and cohesion in object-oriented sys- tems. the International Symposium on Applied Corporate Computing (1995)

    1995

  14. [14]

    URL: http://martinfowler

    Lewis, J., Fowler, M.: Microservices: a definition of this new architectural term (2014). URL: http://martinfowler. com/articles/microservices.html (2014)

    2014

  15. [15]

    In: [1993] Proceedings First International Software Metrics Symposium

    Li, W., Henry, S.: Maintenance metrics for the object oriented paradigm. In: [1993] Proceedings First International Software Metrics Symposium. pp. 52–60. IEEE (1993)

    1993

  16. [16]

    Gamifying Architectural Governance to Reduce Organizational Coupling in Microservice Systems

    Li, X.: Gamifying architectural governance to reduce organizational coupling in microservice systems. In: Proceedings of the 5th Workshop on Gamification in Software Development, Verification, and Validation (Gamify2026). ACM (2026), arXiv:2604.22454

    work page internal anchor Pith review Pith/arXiv arXiv 2026

  17. [17]

    Computing107(4), 1–35 (2025)

    Li, X., d’Aragona, D.A., Cerny, T., Lenarduzzi, V., Taibi, D., Janes, A.: Exploring microservice ownership and organizational coupling in open-source projects: an empirical study. Computing107(4), 1–35 (2025)

    2025

  18. [18]

    In: International Conference on Product- Focused Software Process Improvement

    Li, X., d’Aragona, D.A., Taibi, D.: Evaluating microservice organizational cou- pling based on cross-service contribution. In: International Conference on Product- Focused Software Process Improvement. pp. 435–450. Springer (2023)

    2023

  19. [19]

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

    Li, X., Mani, N., Rodriguez, J.S., Cerny, T.: Key developer roles and organizational coupling in microservices: A longitudinal analysis. In: Proceedings of the 30th International Conference on Evaluation and Assessment in Software Engineering (EASE’26). ACM (2026), arXiv:2604.25804

    work page internal anchor Pith review Pith/arXiv arXiv 2026

  20. [20]

    In: 2026 IEEE International Conference on Software Architecture (ICSA’26)

    Mani, N., Sosa, J., Li, X., Cerny, T.: Organizational coupling as a leading indicator of microservice architecture degradation. In: 2026 IEEE International Conference on Software Architecture (ICSA’26). IEEE (2026)

    2026

  21. [21]

    In: Proceedings of the 16th Brazilian Symposium on Software Com- ponents, Architectures, and Reuse

    Moreira, M.G., De França, B.B.N.: Analysis of microservice evolution using cohe- sion metrics. In: Proceedings of the 16th Brazilian Symposium on Software Com- ponents, Architectures, and Reuse. pp. 40–49 (2022)

    2022

  22. [22]

    O’Reilly Media, Inc

    Newman, S.: Building microservices: designing fine-grained systems. " O’Reilly Media, Inc." (2021)

    2021

  23. [23]

    Communications of the ACM15(12), 1053–1058 (1972)

    Parnas, D.L.: On the criteria to be used in decomposing systems into modules. Communications of the ACM15(12), 1053–1058 (1972)

    1972

  24. [24]

    In: 2008 15th Asia-Pacific Software Engineering Conference

    Shim, B., Choue, S., Kim, S., Park, S.: A design quality model for service-oriented architecture. In: 2008 15th Asia-Pacific Software Engineering Conference. pp. 403–

    2008

  25. [25]

    Spinnaker Community: Spinnaker governance repository.https://github.com/ spinnaker/governance(2020),https://github.com/spinnaker/governance, ac- cessed: 2025-10-19

    2020

  26. [26]

    IBM systems journal13(2), 115–139 (1974)

    Stevens, W.P., Myers, G.J., Constantine, L.L.: Structured design. IBM systems journal13(2), 115–139 (1974)

    1974

  27. [27]

    Wohlin, C., Runeson, P., Höst, M., Ohlsson, M.C., Regnell, B., Wesslén, A., et al.: Experimentation in software engineering, vol. 236. Springer (2012)

    2012

  28. [28]

    Prentice-Hall, Inc

    Yourdon, E., Constantine, L.L.: Structured design: fundamentals of a discipline of computer program and systems design. Prentice-Hall, Inc. (1979)

    1979