liveBook · Manning

Distance

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

Distance is the amount of technical and organizational coordination required for related parts to implement a change together.

Distance is the socio-technical coordination required for related parts to change together. It is one factor in coupling pain: Pain = Strength × Volatility × Distance. section 12.1

Distance grows across both organizational and technical boundaries:

  • Organizationally, teams reporting to different managers or working in different offices may need more coordination. section 12.1
  • Technically, distance ranges from variables in one function to classes in one codebase and classes in separate microservices or codebases. section 12.1

Local change versus coordinated deployments

Changing a few lines in one function may involve one team; changing two codebases integrated over a network may require coordinated changes and deployments across two teams. section 12.1

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Defines organizational and technical distance and illustrates a scale from variables in one function to separate microservices.
Examples
Contrasts variables in one function with classes across codebases, and teams with differing managers or office locations.
What you can do after
Evaluate coupling costs by assessing coordination distance alongside strength and volatility.
How it connects
Connects distance to coupling strength, volatility, coupling pain, and socio-technical coordination.

Also explained in

Compare how 10 books explain distance →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.