A Monorepo vs Manyrepos: The ORO way

Transcript

1. This Document is Confidential
2. This Document is Confidential Monorepo vs Manyrepo The ORO way Sergey Zhuravel sergeyz@github
3. This Document is Confidential The Oro Monorepo 17 packages, 100000+ commits Lines of Code (LOC) 1697373 Comment Lines of Code (CLOC) 357480 (21.06%) Non-Comment Lines of Code (NCLOC) 1339893 (78.94%) Logical Lines of Code (LLOC) 401450 (23.65%) Structure Namespaces 5705 Interfaces 594 Traits 122 Classes 15220 Abstract Classes 509 (3.34%) Concrete Classes 14711 (96.66%)
4. Distribution before 5 {package}-dev and {package}-application repos for each of 5 main package combination
6. Distribution before Packages using submodules
8. Distribution before Bamboo (without feedback to github PRs) A lot of manual work to check that builds are ok
11. Development before Backward incompatible and total refactorings required a lot of job to do
13. Development before A lot of context switches between {package}-dev repos
14. Distribution after 5 applications and 17 packages together
19. Development after Backward incompatible changes Old API removals and updates Remove deprecations Documentation Bugfix all packages same time
22. Development after Code review Team collaboration
24. Development after Continuous integration
27. Development after Productivity No switching between repos Shared DX
29. Development after Less management, common tools Easy dependency management
37. This Document is Confidential Summary Advantages Productivity Simpler development flow (development and review) All-in-one approach Fast, unified CI feedback Better DX (less time for deployment and installation, more code examples) Disadvantages dev.json management (should be automated) Short history in case tree was imported Symlinks on Windows =)
38. No wrong coupling and wrong classes usages in packages ATM. Do unit testing, bro! Many thanks to "A Monorepo vs Manyrepos" by Fabien Potencier