How about, you can have microservices back when the engineers/architects care in the slightest about defining domains between services and having a direction or

How about, you can have microservices back when the engineers/architects care in the slightest about defining domains between services and having a direction or overall idea for how they communicate. It's easy to get to a point where you have a big ball of mud of 100 micro-services where each new features touches 20 of them, and just hack in whatever new APIs everywhere that's needed to push a new feature out (but probably buggy due to async state and race conditions that noone was trained enough to figure out up front). All that is pretty equivalent to what you talk about with monoliths.