ʞǝǝƃʎlloʇoʇ@What is your take on the #monorepo paradigm when talking about 100-ish services? 🤔
✅ Is it good?
❌ Is it bad?
Would you use it for non-monolithic architecture?
Any input and RT would be appreciated, so I can gather as many viewpoints as possible. 🙌
Toby@totollygeek it’s no worse than a monolith which is hiding 100 services.
I think my biggest concern would be if there are massive differences in testing/deployment. I’ve found with monorepo projects there are the bits people architect for, and the bits people shoehorn.
RenéWiersma@totollygeek One repo per bounded context I would say. Things that change together should be close together. Things that do not change together should not be close together.
Reinhard Lackner@totollygeek it vastly depends on how big the team behind all those services are. if your in the hundreds than please, by all means go the one repo per bounded context. if your just a handful than I'd go the monorepo route.