Splitting into services enforces nothing if they share a database; splitting into modules with a checked dependency rule enforces more. A build failure on a cross-module import is…
The question was how to deploy four services, and the answer arrived before it. Naming what you actually need — scheduling, health, rolling deploys, secrets.
Two deployables writing the same tables is one service with extra steps. Deciding who owns them is the whole decision, and the intermediate state lasts.
An architectural boundary that exists only in a diagram is a boundary that has already been crossed, and the enforcement is a morning’s work. A violation becomes a…
Pulling a service out of a monolith is a distributed systems problem and a refactoring problem at once, and the refactoring is what determines whether the result is…
Pulling a service out of a monolith is a distributed systems problem plus a refactoring problem at the same time, and the refactoring is the part that determines…