I can't say I agree with all your "okays", although If you prefix them with "In some cases it's okay", then I understand where you're coming from. The problem

I can't say I agree with all your "okays", although If you prefix them with "In some cases it's okay", then I understand where you're coming from. The problem is when it's OK and for how long. If you have a team of people working with a codebase with all those "okays", then they have to be really good developers and know the code inside out. They have to agree when to refactor a business login out instead of adding a hacky "if" condition nested in another hacky "if" condition that depends on another argument and/or state. I guess what I'm trying to say that if those "okays" are in place, then there's a whole bunch of unwritten rules that come in place. But I agree that microservices certainly aren't free (I'd say they are crazy expensive) and modules aren't free either. But all those "okays" can end up costing you your codebase also.