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 “Hands-on Design Patterns with Kotlin” book and “Web Development with Kotlin” course

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