--- title: "TechLab_Report19: Tools and technology - monorepos" description: Read how monorepos can help foster a culture of collaboration, enable continuous integration allows for changes to be made to several components of your overall system, in sync. image: https://content.red-badger.com/hubfs/toolsandtechnology_blogimage-6.jpg --- [![Red Badger](https://content.red-badger.com/hs-fs/hubfs/RB_digital_Logos_RGB-NEW%20RED-AC.png?width=568&height=143&name=RB_digital_Logos_RGB-NEW%20RED-AC.png "Red Badger")](https://red-badger.com?hsLang=en) ![glasses__cleanup_srgb](https://content.red-badger.com/hs-fs/hubfs/glasses__cleanup_srgb.jpg?width=4576&name=glasses__cleanup_srgb.jpg "glasses__cleanup_srgb") # Part of the TechLab_Report19 [![Back to overview](https://no-cache.hubspot.com/cta/default/4210858/2c0c9976-e609-4ef8-a28c-c292a4d255bd.png)](https://cta-redirect.hubspot.com/cta/redirect/4210858/2c0c9976-e609-4ef8-a28c-c292a4d255bd) ![mono_x2-2](https://content.red-badger.com/hs-fs/hubfs/mono_x2-2.png?width=115&name=mono_x2-2.png "mono_x2-2") # Monorepos The traditional way of managing your organisation or department’s codebase – the sum of all the different kinds of code that contribute to your product – is to store each component, service, tool, [infrastructure](https://content.red-badger.com/techlab-report-19/our-specialisms/infrastructure?hsLang=en) or testing automation separately, each in their own repository. This is clearly inspired by the way open source software development is done, where every small tool or library is built by a different person or team. In many organisations, this is often not the case. Frequently, the same group of people work on all of these things together, which allows for a much more light-weight management of the various components and their mutual dependencies, enabling the removal of strict repository boundaries and instead of storing all of your codebase in a single repository – a so-called ‘monorepo’. Monorepos have several benefits compared with the traditional strategy, recently dubbed ‘poly-repo’. To start with, everyone has visibility of the entire codebase and can contribute (with review) to every part of it, helping to foster a [culture of collaboration](https://content.red-badger.com/techlab-report-19/common-problem-areas/engineering-culture?hsLang=en). [Continuous integration and delivery](https://content.red-badger.com/techlab-report-19/our-engineering-principles/continuous-delivery-just-in-time-decisions?hsLang=en) systems can be set up once for everyone. And having a single timeline of changes allows for changes to be made to several components of your overall system, in sync. Knowing the dependencies between the components, these can be [automatically tested](https://content.red-badger.com/techlab-report-19/our-specialisms/testing-and-quality-assurance?hsLang=en), even against all of their known consumers, drastically reducing the feedback time on changes made, when compared to the traditional, semi-manual versioned release workflow. As long as your automated testing is thorough, broken changes don’t even make it into the master branch, let alone in front of customers. With tools like [Kubernetes](https://content.red-badger.com/techlab-report-19/tools-and-technology/kubernetes?hsLang=en), [Istio](https://content.red-badger.com/techlab-report-19/tools-and-technology/service-mesh?hsLang=en), and [Terraform](https://content.red-badger.com/techlab-report-19/tools-and-technology/terraform?hsLang=en) all [the code contributing to your product](https://content.red-badger.com/techlab-report-19/our-engineering-principles/everything-as-code?hsLang=en) can be stored together and changed together, allowing you to treat a distributed application [like a monolith](https://blog.red-badger.com/deploy-a-microservices-application-as-though-it-was-a-monolith?hsLang=en). The boundaries of various applications and systems are also more flexible this way, enabling easy changes in ownership and helping you avoid the pitfalls of the infamous [Conway’s Law](https://en.wikipedia.org/wiki/Conway%27s_law). Tooling for monorepos is still not as well developed as we’d like, but there’s a clear trend towards teams joining their poly-repos together and the tooling (e.g. GitHub) improves to follow. The only remaining issue to solve if your organisation grows to a large scale (we’re talking hundreds of engineers over several years) is scaling the repository management service to match. But fortunately, the industry giants have blazed that trail for us and can offer some solutions. Our take on monorepos? They make the development of moderately complex systems [faster](https://content.red-badger.com/techlab-report-19/common-problem-areas/delivery-speed-and-agility?hsLang=en). They make thorough continuous integration and automated testing easier. And they lower the barriers to safely sharing code across projects. Plus, they’re a good [strategic choice](https://content.red-badger.com/techlab-report-19/common-problem-areas/strategic-direction?hsLang=en) for a flexible source code management strategy – one that’ll set you up for the future. ## Read about other Tools and Tech: - [Kubernetes](https://content.red-badger.com/techlab-report-19/tools-and-technology/kubernetes?hsLang=en) - [Service mesh](https://content.red-badger.com/techlab-report-19/tools-and-technology/service-mesh?hsLang=en) - [React Native](https://content.red-badger.com/techlab-report-19/tools-and-technology/react-native?hsLang=en) - [Golang (Go)](https://content.red-badger.com/techlab-report-19/tools-and-technology/golang?hsLang=en) - [Docker](https://content.red-badger.com/techlab-report-19/tools-and-technology/docker?hsLang=en) - [Terraform](https://content.red-badger.com/techlab-report-19/tools-and-technology/terraform?hsLang=en) - [Statically typed languages](https://content.red-badger.com/techlab-report-19/tools-and-technology/statically-typed-languages?hsLang=en) - [Deconstructed CI services](https://content.red-badger.com/techlab-report-19/tools-and-technology/deconstructed-ci-services?hsLang=en) - [Design systems](https://content.red-badger.com/techlab-report-19/tools-and-technology/design-systems?hsLang=en) [![Back to overview](https://no-cache.hubspot.com/cta/default/4210858/2c0c9976-e609-4ef8-a28c-c292a4d255bd.png)](https://cta-redirect.hubspot.com/cta/redirect/4210858/2c0c9976-e609-4ef8-a28c-c292a4d255bd) ![groupshot_1024](https://content.red-badger.com/hs-fs/hubfs/groupshot_1024.png?width=2000&name=groupshot_1024.png "groupshot_1024") Enjoyed our report? Sign up now to our upcoming event on May 16th - **“Moving at light speed with continuous delivery”** View our [Privacy Policy](https://red-badger.com/privacy-policy?hsLang=en) to find out more about how we take care of your personal data. Copyright © Red Badger Consulting Limited 2026 --- 4th Floor, 2 Old Street Yard, London. EC1Y 8AF [hello@red-badger.com](mailto:hello@red-badger.com) [+44 (0) 20 3567 0555](tel:00442035670555) - [* * ](https://github.com/redbadger) - [* * ](https://twitter.com/redbadgerteam) - [* * ](https://redbadger.typeform.com/to/cBuJUl) - [* * ](https://www.linkedin.com/company/red-badger) - [* * ](https://www.instagram.com/redbadgerteam/) - [* * ](https://www.facebook.com/RedBadger) - [* * ](https://www.youtube.com/redbadgerteam) - [* * ](https://plus.google.com/+Redbadgerteam) - [* * ](https://red-badger.com?hsLang=en) ![](https://px.ads.linkedin.com/collect/?pid=3519985&fmt=gif)