Layered systems do not have to be 'monolithical'. Note that we're both at this moment using layered systems to have this conversation. > A layered monolith ca

Layered systems do not have to be 'monolithical'. Note that we're both at this moment using layered systems to have this conversation. > A layered monolith can still easily have random people cut across boundaries without you knowing because there are hundreds of engineers all working in the same system. I appreciated your final word regarding "social reasons" and I think we're in strong agreement in that regard. In the final analysis, it seems accurate to say that Microservices approach permits runtime operational [micro] payments towards organizational and analytical debt [1]. The hypothetical system(/straw man?:) you posit above is indicative of organizational, not architectural, failure/deficiency. [1]: in the 'technical debt' sense.