As Fulfillment separates from the monolith, supporting capabilities appear that don't fit neatly inside it. Which deserve a boundary of their own, and which are just shared code?
This article is part of ZibiWorks, an ongoing fictional modernization case study. The ZibiWorks site is the canonical home of the series, with the full company context, starting architecture, and related installments. Explore the full series at ZibiWorks .
In Installment 04: Boundaries and Meaning we identified the business boundaries inside ZibiWorks. In Installment 05: The First Seam we established the first technical seam around Fulfillment, giving us a way to evolve its implementation without forcing the rest of the monolith to change alongside it.
Identifying boundaries is only part of the problem.
The next boundary problem
As we separate Fulfillment from the monolith, we keep running into functionality that doesn't sit cleanly inside its core business responsibilities. Some of it supports several domains.…