Modularity

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

A modular architecture organizes a system into separable modules with well-defined responsibilities and limited dependencies between them.

Modularity separates a system into parts that teams can understand and change without routinely disrupting unrelated work. Its value becomes clear when a growing system slows compilation, testing, deployment, and onboarding—and when changes in one area break another. Looser coupling and ownership of system parts can help restore the ability to innovate. section 10.4

A category system under strain

Vinted’s marketplace expanded beyond women’s clothing into six departments. Its category tree needed to grow deeper and wider, but the existing architecture blocked a newly formed categories team from delivering value. Engineering leaders agreed that a loosely coupled, modular architecture, paired with teams owning parts of the system, was needed. section 10.4

Team boundaries and software boundaries may not change at the same pace. During a phased transition, teams can still share technical artifacts and need closer collaboration. At CloudSuite, a backend API crossed team boundaries; because physically separating it required considerable effort, collaboration and modularization within the component came first. section 17.4

Figure 17.5 In phase 1 of the inverse Conway maneuver, teams were reorganized first.

The first-phase diagram shows why reorganizing teams does not immediately remove dependencies in the existing architecture. section 17.4

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

How deep it goes

Explains the organizational rationale and a phased transition, but does not specify how to implement module boundaries.

Examples

Uses Vinted’s expanding category tree and CloudSuite’s shared backend API to show different pressures on modularity.

What you can do after

Practice/perform phased modularization by planning collaboration where team boundaries still cross shared technical artifacts.

How it connects

Connects modularity to loose coupling, team ownership, and the inverse Conway maneuver.

liveBookmanning.com

Read Architecture Modernization: Socio-technical alignment of software, strategy, and structure on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  React Quickly, Second EditionA software architecture that organizes functionality into reusable, loosely coupled components with separated responsibilities.
• 

  liveBookmanning.com
  Get Programming: Learn to code with PythonModularity is the organization of software into separate components with distinct responsibilities and interfaces.
• 

  liveBookmanning.com
  Functional Design and Architecture: Examples in HaskellModularity is a structural property in which a program is divided into relatively independent parts with separable responsibilities.
• 

  liveBookmanning.com
  Software Security for DevelopersA modular monolith is a single application organized into well-defined independent modules that communicate through clean interfaces and own specific domains or features.
• 

  liveBookmanning.com
  The Joy of JavaScriptA software design approach that structures a program as separate modules with well-defined responsibilities and interfaces.
• 

  liveBookmanning.com
  Functional Programming in Scala, Second EditionA modular program is composed of components whose meanings and reuse can be understood independently and combined through explicit composition rules.
• 

  liveBookmanning.com
  The Well-Grounded Rubyist, Fourth EditionModularization is the organization of software functionality into separate reusable modules.
• 

  liveBookmanning.com
  Introduction to Generative AI, Second EditionA modular architecture divides a system into separate components that perform distinct functions and can be designed or modified independently.
• 

  liveBookmanning.com
  Building LLM Applications with DSPyModular organization is a structural pattern that separates an application into composable components with distinct responsibilities.

Compare how 10 books explain modularity →

Related concepts

• functionuses · A function is a defined operation that maps inputs to outputs and, when implemented as a callable program unit, may also produce effects.
• Reactused by · React is an open-source JavaScript library for building user interfaces from declarative, reusable components.
• lazy evaluationaddressed by · Lazy evaluation is an evaluation strategy that defers computing an expression or value until its result is needed, potentially avoiding the computation entirely.
• DSPypart of · DSPy is a Python framework for declaratively programming, composing, evaluating, and optimizing language-model applications and pipelines.
• monolithic architecturekind of · Monolithic architecture is a software architecture in which an application's major functionality is organized and deployed as a single integrated unit.

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.