What is a “distributed monolith” and how do you avoid it?

Answer

It’s a system split into services, but still tightly coupled (shared DB, synchronous chatty calls, coordinated deployments). Avoid it by clear ownership, async where appropriate, stable contracts, and independent deployability.