"Do we have to release often? No, we do not, because the release process almost never changes and there are so few components." This is non-sequitur: release f

"Do we have to release often? No, we do not, because the release process almost never changes and there are so few components." This is non-sequitur: release frequency is not dictated by release process - although it is affected by it - but by business requirements. "We never really had “monoliths” before in development that I experienced". Good for the OP, I guess. I currently involved in development of 3 monolith services. All are 6-7 years behind on the framework they were based on and making any sweeping refactorings is cost prohibitive and tantamount to a full rewrite. Were they architected as microservices (which entails not just code, but infra), major refactorings would've been on the table. Code review policy feelings doesn't make a lot of sense to me either. Company's policy is all code goes through review. How one feels about it is not relevant, it's a part of one's job. Microservices or not, code gets reviewed.