
Habib Ur Rehman
Sep 25, 2026
We recently set up our product as a monorepo. Our customer app, admin dashboard, backend and marketing site now all live in one repository. It wasn't an obvious choice at first, so I want to share why we did it and what we've learned along the way.
Why we chose it — Most features touch more than one app. With separate repos, that meant 3 PRs, 3 reviews and a lot of "which version works with which?" With a monorepo, it's one PR and one review, and everything ships together.
What's been great — shared code written once, atomic changes, easier onboarding, one setup.
What's been hard — slow CI without smart caching, blurred boundaries, deploys that need care, and a repo that grows fast.
My take: a monorepo isn't "better." It's a trade-off. Choose the structure that fits your team, not the trend.
#SoftwareEngineering #Monorepo #SystemDesign #WebDevelopment
View on LinkedIn


















