Working on a microservices project currently. It is very well designed. Although i think this is not because of it being microservices. It is because of the tea

Working on a microservices project currently. It is very well designed. Although i think this is not because of it being microservices. It is because of the team of skilled engineers. Using microservices is complete overkill here. Lots of DevOps, hard to get the mental picture for new people. Also we share a lot of code between the repo's. That shared code is in a separate repo. Splitting of code from one repo and putting it in another repo. Refactoring tools dont like it that much. The quality of the code base is what matters and that is quite alright here. I liked this line in the article: _But you should always remember; a well designed codebase can always be switched to microservices, as and when you approach the threshold._ I will remember that when I design a new monolith: every "application" in that monolith should be able to stand on its own. Every PR will be reviewed like that.