liveBook · Manning

Experimental decoupling

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

Experimental decoupling is an exploratory modernization technique that attempts to separate a code area in order to learn its migration difficulty and dependencies.

Experimental decoupling is a deliberately rough extraction attempt used to discover how difficult a code area will be to migrate. It prioritizes learning over safe delivery: engineers may try several approaches, tolerate compiler errors, and work without small steps or unit tests. section 12.4.3

A practical experiment can involve:

  • Choosing a concept believed to be a candidate for a separate microservice. section 12.4.3
  • Deleting the concept from the codebase and following the resulting compiler errors. section 12.4.3
  • Introducing an interface that could later replace local implementation calls with API calls. section 12.4.3
  • Using the failed or chaotic attempt to replace optimistic assumptions with a realistic view of complexity. section 12.4.3

Testing the creatives boundary

An engineer working in a legacy monolith attempted to extract creatives as a microservice. After a week of deleting code, repairing compiler errors, and exploring an interface boundary, the experiment revealed substantial coupling between the code and database. section 12.4.3

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

How deep it goes
Demonstrates exploratory extraction through compiler feedback and interfaces, but stops short of a safe, tested migration.
Examples
Uses a creatives extraction attempt involving code deletion, compiler repair, interface design, and database coupling.
What it assumes
Assumes access to a codebase and a concept being considered for extraction as a separate service.
What you can do after
Evaluate migration difficulty and dependencies with more realistic expectations before choosing modernization work.
How it connects
Links legacy monoliths, microservices, interfaces, APIs, databases, and compiler errors.
Cover of Architecture Modernization: Socio-technical alignment of software, strategy, and structure
liveBookmanning.com
Read Architecture Modernization: Socio-technical alignment of software, strategy, and structure on liveBook Get the book at manning.com

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.