Concrete Coupling

Kind: anti-pattern

Layer: Enforcement Core

Aliases: Concrete Dependency

Record: architecture:concrete-coupling

Severity: discouraged

Scope: modularity

Formed by: Let high-level policy depend directly on low-level implementations, vendor APIs, framework classes, or concrete constructors, then spread those concrete assumptions across the core.

Canonical: Ontology

A defect in which high-level policy depends directly on concrete implementations instead of on abstractions.

Listed in Architecture principles, after God Object and before Schema Drift.

Refactored by

• Extract Interface
• Introduce Port
• Extract Adapter
• Dependency Injection
• Invert Dependency

Severity

• discouraged

Category

• Anti-patterns

Force

• Modularity

Negated by

• Interface-Based Design
• Abstraction
• Replaceability
• Dependency Inversion Principle

Violates

• Interface-Based Design
• Abstraction
• Dependency Inversion Principle
• Ports and Adapters Architecture

Linked from

• The direction axis
• Anti-patterns
• Contracts / Interfaces / Compatibility
• Core Modular Design
• SOLID / Object-Oriented Design
• Codebase / System Architecture Styles
• Codebase / System Architecture Styles
• SOLID / Object-Oriented Design
• Severity levels
• The forces