3 ms·
> We're pretty small scale (< 20 services, < 10 devs) This is really important and the whole point, indeed. Eg: We consider our org to be "many repos" (we hav
by shados 8y ago
> We're pretty small scale (< 20 services, < 10 devs)
This is really important and the whole point, indeed.
Eg: We consider our org to be "many repos" (we have several thousands). However, hundreds of them contain 5, 10, or 20+ packages/projects/services. It's funny because we'll talk about creating "monorepos" (plural) for certain part of our product, and it confuses the hell out of people.
- aidos 8y agoSeveral thousand repos - ye gads! How do you document them? How do they fit together? Do they reference each other?
- shados 8y agoThe answers to all those questions are "it depends". There's a few thousand libraries, those obviously refer to each other.. Some have readme files and that's enough, some have full documentation "books", some have comments in the code and that's enough. We don't mandate a company wide development process, so each team and groups can choose their own process and how they track their stuff. We do have automation and tooling to keep track of things though.
- gowld 8y agoYou are talking about creating "oligorepos".
- robaato 8y agoMaybe an "omnirepo"?! (Though risks connotations with "omnishambles" - https://en.wikipedia.org/wiki/Omnishambles https://en.wikipedia.org/wiki/Omnishambles