>> If you are separating functionality using functions, the compiler helps you spot problems. > Maybe you could be more specific? I don't see how a compiler wi

>> If you are separating functionality using functions, the compiler helps you spot problems. > Maybe you could be more specific? I don't see how a compiler will help prevent coupling of modules/ internal components. A super simple but effective way compilers prevent bad behavior is by preventing circular includes/imports. In a programming language, if module A imports module B, then module B can't easily import module A.* The compiler/interpreter will complain about circular/infinite imports. This general rule motivates developers to organize their code hierarchically, from high level abstractions down to lower level, and militates against inter-dependencies. In contrast, there's nothing to stop microservice A from contacting microservice B, which in turn contacts back to microservice A. It's so easy to do, that many will do it without even realizing it. If you're developing microservice B, you may not even know that microservice A is using it. Designed correctly, microservices can be another great way to separate functionality. The problem is actually designing them correctly, and keeping that design enforced. * Sure, there are ways of effectively doing circular imports in programming languages, but they usually require some active choice by the developer. It's hard to do it by accident.