Independence

Kind: principle

Layer: Structural Core

Record: architecture:independence

Severity: recommended

Scope: module, service, deployment

Canonical: Ontology

A design rule that a module can be tested and deployed without the modules around it being present or released.

Listed in Architecture principles, after Interchangeability and before Autonomy.

Requires

• Low Coupling
• Explicit Boundaries

Reinforces

• Autonomy
• Portability

Enables

• Independent Testing
• Independent Deployment

Conflicts with

• Shared Runtime Dependency

In tension with

• Coordination Cost

Tensions

• Independence / Coordination Cost

Violated by

• Shared Database
• Synchronous Chain Trap

Refactored by

• Split Bounded Context
• Domain Events
• Introduce Port

Severity

• recommended

Category

• Core Modular Design

Linked from

• Template families
• Domain Architecture
• Contracts / Interfaces / Compatibility
• Portability / Infrastructure / Deployment
• Core Modular Design
• Codebase / System Architecture Styles
• Core Modular Design
• Core Vocabulary
• Domain Architecture
• Event Messaging Async
• Severity levels
• The resolutions