Member-only story
Code organisation is one of the biggest discussions in Software. And similar to most things, it is subjective and the TDLR with this post is this — “choose what works well for your team, but don’t be afraid to try out different things.”
In this post, I want to discuss the basics of a mono-repo and why you could consider it over poly-repos.
What are mono-repos?
Stated simply, mono-repos are code repositories which house more than one deployable. These deployables could be an npm package, a web app, a docker image, a helm template, a shell script, etc., or a combination of these.
Also, this means everything in your project is placed in one repository — these include the source code, documentation, supporting examples (postman collections, curl scripts), CI/CD, and the rest.
Why mono-repos?
This is where the discussion starts, and I encourage each one of you to share your thoughts about mono-repos in the comments.
I understand that this is very subjective but let’s try and list out reasons why mono-repos might be a good idea.
Transparency/Openness
The main reason why mono-repos make sense, as everything is in one place, the complete code base, and…
