Monorepo, Polyrepo And Micro-Frontends Explained
03 Aug 2026
31 min read
On this page
- First, two words that get conflated
- Polyrepo: one repository per application
- A day in the life: changing a shared button
- What polyrepo genuinely buys you
- What it costs
- Monorepo: one repository, many packages
- The one misconception to kill first
- How the pieces know about each other
- The same day in the life
- What it costs
- Micro-frontends: independent deploys, assembled at runtime
- How the pieces actually meet
- What micro-frontends genuinely buy you
- What they cost
- They are two axes, not one choice
- The real question: where should it break?
- Two scenarios
- Scenario one: three portals, three teams
- Scenario two: one person, three products
- The question that settles it
- Myths worth dismantling
- Choosing, in practice
- Migrating, in either direction
- The thing underneath
Related Articles
The Model That Cannot Write A Sentence
TypeSafe AI came out of stealth with Jev, a frontier model that produces no text at all — it picks one option from a list you supply and tells you how sure it is. The speed claims are 20-200x, and they are both real and quoted at the wrong altitude. This is what the architecture actually changes, why a live virtual try-on is the demo that flatters it most, how a 40ms repaint is possible at all, and the comparison the launch post declines to run.
Read article
How to setup a Nextjs 14 custom server
Steps to setup custom Next.js server
Read article