How Vercel adopted microfrontends - Vercel
vercel.com · 1,355 words · saved by 1 readers
Learn how Vercel cut build times and improved developer velocity while maintaining a smooth user experience with microfrontends.
Learn how Vercel cut build times and improved developer velocity while maintaining a smooth user experience with microfrontends. Vercel's main website, once a single large Next.js application, serves both our website visitors and logged-in dashboard. But, as Vercel grew, this setup revealed opportunities for improvement. Build times grew, dependency management became more intricate, and workflows needed optimization. Minor changes triggered full builds, affecting isolated development and CI pipelines. It was clear a change was needed. By rethinking our architecture, we shifted to vertical micr
related reading
- 5 Things I Learned From 5 Years At Vercel | Lee Robinsonleerob.com
- How we rebuilt Next.js with AI in one weekblog.cloudflare.com
- The Conductor Rewrite: What They Changed to Make It Fastperformance.dev
- What does Vercel do? - Vercelvercel.com
- Micro Frontends - extending the microservice idea to frontend developmentmicro-frontends.org
- The Descent — What Happened to the Frontend While You Weren't Watchingdavidpoblador.com
- What will you ship?rauno.me
- How Mozilla’s Rust dramatically improved our server-side performance | Figma Blogfigma.com
- How to scale a large codebase - Vercelvercel.com
- The new wave of Javascript web frameworksfrontendmastery.com
- krish's blog • So I rebuilt Vercel...krish.gg
- When Micro-Frontends Aren't the Right Choice | Szymon Chudychudy.me