mlsanityData to 14 Oct 2026

Evaluating Microservice Organizational Coupling based on Cross-service Contribution

arXiv 2309.03552 ↗First posted 7 Sep 2023cs.SEcited by 1

Not on the map. Why?

Abstract (arXiv)

For traditional modular software systems, "high cohesion, low coupling" is a recommended setting while it remains so for microservice architectures. However, coupling phenomena commonly exist therein which are caused by cross-service calls and dependencies. In addition, it is noticeable that teams for microservice projects can also suffer from high coupling issues in terms of their cross-service contribution, which can inevitably result in technical debt and high managerial costs. Such organizational coupling needs to be detected and mitigated in time to prevent future losses. Therefore, this paper proposes an automatable approach to evaluate the organizational couple by investigating the microservice ownership and cross-service contribution.

Key facts. Cited by 1 paper in the map (data through 14 Oct 2026). First posted on arXiv 7 Sep 2023.

Builds on

No reference list yet.

Built on by

Cited by year

Citing papers per year: 2024: 1.

1 paper.