liveBook · Manning

Seam

A software seam is a boundary where behavior or dependencies can be varied, replaced, or isolated with limited disruption to the surrounding system.

How 3 Manning books explain it

The Art of Unit Testing 3e

A seam is a location in code where behavior or dependencies can be replaced for testing.

How it is used
Provides a replaceable boundary for controlling dependencies and checking behavior in tests.
How deep it goes
Defines seams and lists injection approaches, while deferring broader design patterns and antipatterns.
Examples
Uses a password verifier's logger call and fake clocks, databases, and networks as dependencies tests may control.
What you can do after
Build it from scratch by introducing a replaceable dependency boundary, such as a logger parameter, for tests to supply a fake.

Read how The Art of Unit Testing 3e explains seam →

Software Architecture Decision-Making

An architectural seam is a deliberate boundary that allows part of a system to vary, be replaced, extended, tested, reconfigured, or modified with limited disruption to other parts.

How it is used
Supports safe evolution by containing changes to volatile dependencies, integrations, workflows, and replaceable capabilities.
How deep it goes
Defines placement rules, boundary mechanisms, messaging trade-offs, and incremental replacement, but avoids universal abstraction prescriptions.
Examples
Uses façades, adapters, gateways, queues, APIs, routing points, and gradual legacy-to-new traffic shifts.
What you can do after
Evaluate replacement readiness by locating volatile dependencies, checking contract stability, and identifying changes that can proceed in slices.

Read how Software Architecture Decision-Making explains seam →

Build High Value Software Systems

A place in a software system where behavior can be altered or substituted without changing the code at that point.

How it is used
Creates testable boundaries in legacy code by separating business logic from external dependencies.
How deep it goes
Defines seams and explains dependency substitution for tests, but provides no concrete implementation sample.
Examples
Uses database, API, and filesystem calls to illustrate dependencies replaced by mocks in tests.
What you can do after
Apply it via an interface or overridable method to substitute test dependencies while keeping business logic unchanged.

Read how Build High Value Software Systems explains seam →

Also covered in

What to know first

Related concepts

Questions about seam

What is seam?

A software seam is a boundary where behavior or dependencies can be varied, replaced, or isolated with limited disruption to the surrounding system.

Which Manning books explain seam?

The Art of Unit Testing 3e, Software Architecture Decision-Making and Build High Value Software Systems.

What should I know before learning seam?

Manning books that teach seam usually introduce refactoring and test-driven development first.

What is the difference between seam and legacy code?

A software seam is a boundary where behavior or dependencies can be varied, replaced, or isolated with limited disruption to the surrounding system. Legacy code is existing software code carried forward from earlier development for maintenance or change, regardless of its test coverage or current usefulness.

What kinds of seam are there?

Kinds of seam include object seam.

What is seam part of?

Seam is part of application code. Application code is software code that implements an application’s intended behavior and functionality.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.