Manu's Vault

Semantic Coupling

3 min readStatus:Seedling

Core Idea

Semantic coupling occurs when components depend on shared business or technical concepts, making changes to these meanings ripple across systems—coupling inherent to the problem domain that cannot be eliminated by design alone.

Definition

Semantic coupling occurs when components depend on shared business or technical concepts, making changes to these meanings ripple across multiple systems. Unlike structural or implementation coupling, semantic coupling represents inherent dependencies in the problem domain itself—coupling that cannot be eliminated because it reflects genuine business logic relationships.

Neal Ford distinguishes semantic coupling as “the inherent natural coupling of a workflow.” In a book ordering system, you must have a catalog, user, inventory, and warehouse. These dependencies are not implementation choices—they’re intrinsic to what an ordering system means.

Key Characteristics

  • Inherent to the domain: Arises from how business concepts naturally relate, not from technical design choices—Payment and Order must coordinate in e-commerce because the business process requires it
  • Changes propagate unavoidably: When domain concept meanings evolve, all coupled components must update
  • Exists at the information level: Created by shared understanding of data meanings and business rules
  • Cannot be eliminated, only managed: Goal is making semantic coupling explicit rather than pretending it doesn’t exist; use bounded contexts to limit scope
  • Distinct from implementation coupling: Technical choices add unnecessary coupling on top of semantic coupling

Why It Matters

  • Architectural honesty: Attempting to “decouple” semantically related components through event buses or message queues only obscures the coupling—it doesn’t eliminate it
  • Design decisions: When complexity of shared semantics is high, centralized orchestration may be more honest than pretending components are independent via choreography
  • Change impact analysis: Semantic coupling predicts where changes propagate—empirical research shows over 70% of semantically related classes co-change
  • Coupling — Semantic coupling is one fundamental type of coupling
  • Implementation-Coupling — Technical coupling choices that add to unavoidable semantic coupling
  • Bounded-Context — DDD pattern that explicitly manages semantic coupling scope
  • Architecture-Quantum — Semantic coupling can span quantum boundaries even when structural coupling doesn’t
  • Dynamic-Coupling — Runtime communication patterns that often reflect semantic coupling
  • Data-Ownership-Patterns - Data ownership boundaries and semantic alignment
  • Contract - Interface design and semantic coupling

Sources

  • Ford, Neal, Mark Richards, Pramod Sadalage, and Zhamak Dehghani (2022). Software Architecture: The Hard Parts - Modern Trade-Off Analyses for Distributed Architectures. O’Reilly Media. ISBN: 9781492086895.

    • Distinction between semantic and implementation coupling

  • Bavota, Gabriele et al. (2013). “A Two-Step Technique for Extract Class Refactoring.” IEEE/ACM ASE. Semantic coupling measured through information retrieval techniques

  • Khononov, Vladik (2020). “Balancing Coupling in Distributed Systems.” DDD Europe Conference. Available: https://www.infoq.com/news/2020/02/balancing-coupling-ddd-europe/

  • Ford, Neal (2019). “Semantic Coupling.” Programming Brain blog. Available: https://programmingbrain.com/2019/01/semantic-coupling

  • Coupling.dev (2024). “Semantic coupling | Balancing Coupling in Software Design.” Available: https://coupling.dev/posts/related-topics/semantic-coupling/

Note

This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.

Graph View

Backlinks