Part 2 of 8 · 1 min read
Seams
Split a piece at a time, along natural lines.
Think of a block of marble. A carver can blow it up, which rarely ends well, or chip pieces away and learn from each cut. BM uses the same picture and advises chipping.
A large monolith tends to be the opposite of what page 6 asked for. Unrelated code sits together, and everything is coupled: a change to one line cannot ship without redeploying the whole system and perhaps affecting the rest.
BM borrows the word seam from Michael Feathers's book on legacy code: a part of the code that can be treated in isolation and changed without touching the rest. Feathers uses seams to clean code up. BM uses them to find service boundaries. A bounded context (page 6) makes an excellent seam, because it is cohesive and loosely coupled to others by definition.
Seam
A seam is a part of a codebase that can be handled on its own, without changing the rest. A good seam can become a service boundary.
Example: all the code for stock levels and dispatching sits in one area with a small, clear set of calls into it. That area is a seam.
Check yourself: 1. Why does BM prefer chipping to a big rewrite? 2. What makes a bounded context a good seam? 3. What is the difference between how Feathers and BM use seams?