EMx 083: Are Monorepos Worth It?
In this episode of Elixir Mix the panel discusses monorepos. They start by defining monorepos and sharing examples of what this looks like. The panelists share the pros and cons of working in a monorepo. They discuss the different projects they worked on using a monorepo and what their experience was like.
Monorepos allow for rapid development. Any developer can pull it down and work on it. They work better for teams who are new with a new project and they are still trying to figure out where everything goes. In situations like these, quality is not a large concern but once quality is a priority monorepos make less sense.
On the other hand, monorepos make it easier for developers to forget that these applications are distinct. It also makes it easy for developers to ignore older versions of applications. The panel considers if monorepos are worth these downsides. The panel considers how monorepos work with Live View. They also discuss using an umbrella project similarly to monorepos.
- Mark Ericksen
- Eric Oestrich
- Josh Adams
- Michael Ries
"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!
- Real-Time In-Camera VFX for Next-Gen Filmmaking | Project Spotlight | Unreal Engine
What is a monorepo?
A single source code repository that has both an API and its client in the same repo or maybe multiple projects that work together but they are sort of distinct and run separately into different run times in the same repo.
When does it make the most sense to use a monorepo?
With a new team and new project where they are still figuring out where everything goes.
How can using monorepos hurt the quality of your applications?
Constant deployment will constant interrupt the application for you clients.
Does the size of your team effect the usefulness of a monorepo?
Yes, monorepos work better for smaller teams.