Distributed Monolith

A distributed monolith occurs when services are physically separated but logically chained. Splitting code into services does not create autonomy when business logic remains coupled. Network boundaries do not fix poor domain boundaries. A coupling audit should precede service extraction. A business rule change in a coupled service system can require many coordinated releases and integration test runs. Distributed monoliths make failures slower and harder to isolate.