Code Shipping - Dependency (Coupling)

> Code - (Programming|Computer) Language > Code Shipping - Change and Deployment Pipeline - Development Lifecycle / Workflow

1 - About

Logical Data Modeling - Dependency (Coupling) in code.

A (module|package|library) often requires other (packages|module) to be installed to function correctly. Such a relation is called a dependency.

Coupling or dependency is the degree to which each program module relies on each one of the other modules.

Dependencies are not only dynamic with modules, there is also static one such as:

A library dependency define an an abstraction layer in your code.


3 - Management

3.1 - Type

3.1.1 - Transitive

A dependency of a dependency is a transitive dependency.

3.1.2 - External

3.1.3 - exported

An exported dependency is a library that will be found in the compile classpath of the consumer (ie exported to the consumer)

3.2 - Visualization

3.2.1 - Graph

3.2.2 - Death Star

Services relationship (ie dependency).

All component are placed on a circle and if they have a dependency you will draw a line between this components. And as you see, you got a sort of big planet of death … Beautiful.


3.3 - Dependency indirection

One reason people use symbolic references (like semantic versioning) is so that we can refer to “anything greater than 2.3.4” and not worry about the specific thing that’s used.

As numerous incidents have demonstrated late-binding in production is evil and no sane Ops person would ever do this. How one developer just broke Node, Babel and thousands of projects in 11 lines of JavaScript

3.4 - Hell


Possible solution is called package relocation

4 - Documentation / Reference