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
- How to scale a large codebase - Vercelvercel.com
- Micro Frontends - extending the microservice idea to frontend developmentmicro-frontends.org
- How we rebuilt Next.js with AI in one weekblog.cloudflare.com
- What does Vercel do? - Vercelvercel.com
- krish's blog • So I rebuilt Vercel...krish.gg
- What will you ship?rauno.me
- Design Engineering at Vercel: What we do and how we do it - Vercelvercel.com
- How we built the v0 iOS app - Vercelvercel.com
- How's Linear so fast? A technical breakdownperformance.dev
- The new wave of Javascript web frameworksfrontendmastery.com
- v0 by Vercel - Build Full-Stack Web Apps with AIv0.dev
- The Conductor Rewrite: What They Changed to Make It Fastperformance.dev