Established
In Optibus, we are generally following a monorepo approach for our projects. Different product modules are organized as a monorepo each, as in our eyes this offers several benefits:
- More efficient code sharing and reusability.
- Consistent development environment.
- Easier cross-project refactoring.
- Improved collaboration.
- Simplified Dependency Management: In our monorepo, we can manage dependencies at the repository level, simplifying the process of keeping everything up to date and avoiding version conflicts.
- Streamlined CI/CD Pipeline: A single CI/CD pipeline that can build and test all our projects simultaneously. This, of course, comes with the drawback of a more complicated CI/CD setup and potentially longer running pipelines.
- Better Code Ownership: It's easier to determine who is responsible for each part of the codebase, which can improve code ownership and accountability.
- Simplified Testing: We can set up end-to-end tests and integration tests that cover the entire application more easily in a monorepo, ensuring that changes in one part of the codebase don't break other parts.
- Codebase Navigation: Developers can easily navigate through different parts of the codebase without having to switch between multiple repositories or projects.