AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: streamline formatting and proofreading

Browse Source
This commit is contained in:
Stefan Rotsch
2023-10-16 12:22:46 +02:00
committed by Stefan Rotsch
parent 2c541dfbea
commit 94ac286c34
43 changed files with 177 additions and 257 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
radar/2023-09-01/monorepo.md
View File

@@ -1,25 +1,22 @@
---
title: "Monorepo"
ring: adopt
quadrant: methods-and-patterns
featured: true
tags: [ coding ]
title: "Monorepo"
ring: adopt
quadrant: methods-and-patterns
tags: [coding]
---
### Why We Consider a Monorepo Approach
Adopting a monorepo approach for our React and Next.js-based projects offers several benefits, _although it may not be
the best fit for every project._
1. More efficient code sharing and reusability
2. Consistent Development Environment
3. Easier Cross-project Refactoring
4. Improved Collaboration
5. **Simplified Dependency Management**: In our monorepo, we can manage dependencies at the repository level, which can
simplify the process of keeping everything up to date and avoiding version conflicts.
1. More efficient code sharing and reusability.
2. Consistent development environment.
3. Easier cross-project refactoring.
4. Improved collaboration.
5. **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.
6. **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 probably longer running pipelines.
7. **Better Code Ownership**: It's easier to see who is responsible for each part of the codebase, which can help
This, of course, comes with the drawback of a more complicated CI/CD setup and potentially longer running pipelines.
7. **Better Code Ownership**: It's easier to determine who is responsible for each part of the codebase, which can
improve code ownership and accountability.
8. **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.
@@ -28,5 +25,5 @@ the best fit for every project._
**However, it is important to note that monorepos are not a one-size-fits-all solution.** They can introduce complexity,
especially in very large projects, and may not be suitable for all team sizes or development workflows. The decision to
adopt a monorepo should be based on careful consideration of your project's specific requirements, team size, and
adopt a monorepo should be based on a careful consideration of your project's specific requirements, team size, and
development practices.