liveBook · Manning

Semantic coupling

As explained in Data-Oriented Programming in Java

Semantic coupling is a dependency in which software structure reflects the meanings, representations, or contracts of external components.

Semantic coupling occurs when a system’s structure mirrors the meanings, representations, or contracts of external components. A pipeline shaped like Service A and Database B inherits boundaries that belong to those systems rather than its own domain. section 10.2

Reduce semantic coupling by:

  • Choosing boundaries from the domain’s data rather than from external APIs. section 10.2

A data-shaped ingestion boundary

An ingestion flow reads manifest entries, transforms cloud files into UpdatesAndInserts, and passes those records to a bulk loader. Repositories and transformers absorb database and file-format details instead of exposing them throughout the system.

How Data-Oriented Programming in Java covers it

How deep it goes
Defines the coupling and works through ingestion abstractions, factories, repositories, transformers, and tests.
Examples
Uses cloud-file ingestion, CSV transformation, database repositories, manifest dispatch, and tests that expose external-system knowledge.
What it assumes
Assumes familiarity with objects, interfaces, repositories, external services, and database-backed ingestion flows.
What you can do after
Apply it by designing data-shaped boundaries that isolate external representations behind transformers, loaders, and repositories.
How it connects
Connects semantic coupling to software architecture, object-oriented programming, data-oriented architecture, abstractions, and factories.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Data-Oriented Programming in Java. The section links point to the parts of the book it draws on.