liveBook · Manning

Adapter

As explained in Software Architecture Decision-Making

An adapter is a component that presents a consistent interface around an external dependency whose interface differs from the application's internal needs.

An adapter isolates known external integrations from core workflow logic without prematurely creating a generalized integration framework. It preserves room for change while keeping the first design proportionate to current evidence. section 3.1

Use an adapter when:

  • External dependencies should not be scattered through business logic. section 3.1
  • The integration is known, but future variations remain uncertain. section 3.1
  • A reusable abstraction can wait until multiple concrete cases reveal a repeated pattern. section 3.1
Table 3.2 Responding to perfection drift
Signal
Diagnostic question
Better response
Over-engineering early
What current problem does this complexity solve?
Remove or defer the part that solves only a hypothetical problem. Keep only the structure needed for the known problem.
Designing for hypothetical future scenarios
What evidence suggests this future is likely soon?
Preserve a seam or decision record but avoid building the full future capability until the signal becomes real.
Building abstractions “just in case”
How many real variations exist today?
Wait until there are at least two or three concrete cases, unless reversal would be very expensive later.
Introducing patterns the team cannot maintain
Can the team operate, debug, and evolve this pattern without external heroes?
Choose a simpler pattern now and define the conditions that would justify moving to the more advanced one later.
Treating architecture as a personal project
Who else needs to understand, support, and change this design?
Bring the team into the decision and make ownership, trade-offs, and support expectations explicit.
Optimizing for an ideal end state instead of current value
What value is delayed by pursuing the ideal version now?
Deliver a focused slice first, then strengthen the architecture as real feedback appears.

Use the decision table to distinguish useful seams from premature abstractions and patterns the team cannot maintain. section 3.1

How Software Architecture Decision-Making covers it

How deep it goes
Defines simple adapters and defers generalized frameworks, implementation details, and reuse until repeated patterns emerge.
Examples
Uses simple adapters around known integrations in an internal workflow system.
What you can do after
Apply it via simple interfaces that keep external dependencies out of core workflow logic.
How it connects
Connects external integrations with business logic, infrastructure boundaries, and modular monolith design.

Also explained in

Compare how 17 books explain adapter →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Software Architecture Decision-Making. The section links point to the parts of the book it draws on.