| What you are describing as the good parts sounds to me as what you get from a traditional monolith. Why build libraries and separate services if an update on some part of the codebase needs changes across all the platform? This trend of microservices + monorepos sound to me like taking the worst part of everything. If you do microservices, then let each team have their own stack, their own tools, their own libraries and be independent and just agree on the APIs. If you want everything super consistent and share as much code as possible, etc then just do a traditional (well architected) monolith, maybe deploy it with different configurations for different scaling needs, etc. Monorepos are to me a symptom of worse problems. I worked for a.company where they had a rule that "every repository should be a monorepo". They didn't even understand everything that was wrong with that rule. |