5 ms·
This hit a little to close to home for me. Haha basic sections is perfect. It is supremely hard to get monorepos right at scale without the right culture, tooli
by dandigangi 5y ago
This hit a little to close to home for me. Haha basic sections is perfect. It is supremely hard to get monorepos right at scale without the right culture, tooling, and gating. But on the microservice side there is a list of clear cons as well. I prefer it but have run into the side of deployments which is difficult getting things in sync at times if you don't have truly isolated services and the testing in the middle to expose failures before anything goes out. Databases are an especially difficult variable when you need to roll out migrations.
- treeman79 5y agoI’ve seen a company move from mono repo to micro services with moderate success. However they had to increase the team size 5x. Most productivity dropped a lot. Although on some of the really hard problems it freed them up enough to be more successful.
- jeffbee 5y ago"monorepo" and "microservices" exist on two orthogonal planes of software development. They can go together or separately and are not related.
- Sohcahtoa82 5y agoYeah, I think some people are confusing "Monorepo" with "Monolith". You can have a monorepo without having a monolith.
- dandigangi 5y agoYeah thats true. Good point. Kind of lost that in my comment.