Related Posts
Additional Posts in Tech
Hi All, I have 3.5 yrs of experience in Product Management and I'm interviewing at JP Morgan chase for Senior Product Manager role and Product Manager role, for Seattle Location. What kind of salary range should I give for each role when the recruiter pops up this question? JPMorgan Chase
New to Fishbowl?
unlock all discussions on Fishbowl.




There's no way for us to truly judge whether this is a right or wrong move. It all depends on why your company wants to do this. What is the intended outcome? Are the stakeholders properly aligned on this? What is the roadmap for developing for this monorepo? Are there proper guidances for all the devs involved planned or in place for the new workflows? Hopefully this wasn't done on a whim.
I joined my team at the tail end of such a migration, so I pretty much only knew it was a monorepo. There were some complaints for sure, but all in all, the monorepo was a net positive. Branch management wasn't really an issue. Each team that owned the individual repos were still owners, so they are still aware of which parts they are working on. We have proper mechanisms in place that notifies the correct owners when a PR is issued so PRs weren't lost. It's nice to be able to search through the PRs histories in 1 repo rather than jumping between repos to find different changes.
This was a nearly year-long project by some staff+ engineers. There's always going to be some pain with a transition of this scale. Proper planning is key. And hopefully the DRI's of this migration have done their due diligence.
A what?
Rising Star
Like instead of a repo for each service, we just have one giant repo with everyone's code in it
Makes kubernetes or Bazel type deployments easier. Makes branch management and PRs a nightmare
We are moving from a monorepo into properly designed microservices.
If they want to do a monorepo I think a cleaner method of adoption is a modular monorepo.
I did this twice at a super small scale at a tiny company l. Huge productivity win.
I was at a large tech company that was moving to micro services and smaller repos. At that scale it makes sense unless you have a dedicated stack to manage at scale (see Google)
Practically you pay for complexity with tooling, and that tooling needs to scale, or you pay with people/organizational.
It was very easy to build on the monorepo at the small company and really hard to do anything due to cross functional ownership in the bigger one.