It's still possible, and arguably good design, to write a monolith as a cluster of separate cooperating internal logical services. That way you can keep the ben

It's still possible, and arguably good design, to write a monolith as a cluster of separate cooperating internal logical services. That way you can keep the benefits of decoupling and ownership boundaries without all the deployment complexity. In Java, OSGi was particularly good for this, but you could easily build it around a fairly simple DI framework in pretty much every major language. The most important thing though is to keep your interfaces well-designed and well-communicated. They are the principal source of bugs and misunderstandings.