Yes, it’s a bad practice. It’s a “boiling frog”. You have this monorepo, but it’s small, only 5 services. So, you add another one. And another. And before you notice, you end up with a distributed monolith.

Of course I don’t know anything about your system. Microservices can go wrong in many ways. Nano-services. Entity-services. You name it. But having a monorepo is a recipe for disaster.


Solutions Architect @Depop, author of “Kotlin Design Patterns and Best Practices” book and “Pragmatic System Design” course

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store