In a city commerce platform, “price” means shelf list price in the catalog team’s model but means amount due after tax and fees in billing. Which decomposition tool should guide where to cut services?
Select an answer to reveal the explanation.
Short Explanation
Bounded context is like different city departments each owning their vocabulary—“price” in catalog is not “price” in billing. Cut where the language stays coherent, and translate at the boundary. A forced global definition becomes a distributed ball of mud.
Full Explanation
Bounded contexts keep a service’s model and ubiquitous language coherent. Crossing contexts without translation mixes meanings and produces a distributed big ball of mud. Global shared tables, traffic-only splits, and inventing PDB-per-route rules are not the 1084 decomposition tool this item targets.