[tomtheelder]

Firmly disagree. Microservices get you very little in terms of code quality enforcement past what you would get with a well modularized monolith, and they introduce a lot of code quality & architectural pitfalls. I think going microservices to enforce boundaries and decoupling is a very bad idea that will create far more trouble than its worth. I'd be a lot more scared of my junior devs committing code to microservices than to a decently organized monolith.

I would only seriously consider a move to microservices for deployment/perf reasons.

[revskill]

You might misunderstand the point here.

It's about how to keep the velocity without firing junior dev, without removing bad code from the production system.

So microservice is a leadership tool to manage it. Keep it in control.