As our web applications grow in complexity, we often find ourselves needing to split them into smaller, more manageable pieces. This is where Next.js Multi Zones comes in - a powerful feature that allows us to create micro-frontends that work together seamlessly. Let's look at how we can use Multi Zones to build scalable and maintainable web applications.

The challenge of growing applications

When a web application scales, we often need multiple teams working on different parts of the site. This can lead to:

Merge conflicts: With multiple teams working on the same codebase, merge conflicts become more frequent, slowing down development and increasing the risk of errors.
Differing scopes and business rules: Different parts of an application may have distinct requirements, making it challenging to maintain consistency across the entire codebase.
Slower development and deployment cycles: As the application grows, building, testing, and deploying the entire application becomes more time-consuming and risky.

The traditional solution? Splitting the application into separate projects and/or setting up a mono-repo. But this often results in a inconsistend user experience and complex deployment processes. What if you want to have completely separate Next.js projects but combine them into a single experience?

How can Next.js Multi Zones help?

Next.js Multi Zones allows us to have multiple Next.js applications work together as if they were a single application. This means:

Independent development and deployment: Teams can work on different parts of the site without interfering with each other, and deploy their sections independently.
Seamless navigation for users: Despite being separate applications, users experience smooth, client-side navigation between zones.

Let's explore how to set this up with a concrete example:

Setting up a Multi Zones

We'll create a project with two zones: 'home' and 'blog'. Here's how to set it up step-by-step:

Create a new directory for your Multi Zones project:

mkdir next-js-multi-zones
cd next-js-multi-zones

Create two Next.js applications, one for 'home' and one for 'blog':

npx create-next-app@latest home --typescript --eslint
npx create-next-app@latest blog --typescript --eslint

Navigate to the 'home' directory and update next.config.js:

home/next.config.js

const nextConfig = {
  async rewrites() {
    return [
      {
        source: '/blog',
        destination: 'http://localhost:3001/blog',
      },
      {
        source: '/blog/:path*',
        destination: 'http://localhost:3001/blog/:path*',
      },
    ]
  },
}

module.exports = nextConfig

Navigate to the 'blog' directory and update next.config.js:

blog/next.config.js

const nextConfig = {
  basePath: '/blog',
}

module.exports = nextConfig

Navigate back to the 'home' directory and edit home/app/page.tsx:

home/app/page.tsx

import Link from 'next/link'

export default function Home() {
  return (
    <div>
      <h1>Welcome to Home</h1>
      <Link href="/blog">Go to Blog</Link>
    </div>
  )
}

Navigate to the 'blog' directory and edit blog/app/page.tsx:

blog/app/page.tsx

import Link from 'next/link'

export default function Blog() {
  return (
    <div>
      <h1>Welcome to Blog</h1>
      <Link href="/">Go to Home</Link>
    </div>
  )
}

Open two terminal windows. In the first, start the 'home' application:

cd home
npm run dev -- -p 3000

In the second, start the 'blog' application on a different port:

cd blog
npm run dev -- -p 3001

Now, you can visit http://localhost:3000 to see the 'home' application, and navigate seamlessly to the 'blog' application using the link.

The reality of Multi Zones

With this setup, you can now:

Develop and deploy the 'home' and 'blog' applications independently: Each team can work on their respective applications without affecting others, leading to faster development cycles and reduced risk of conflicts.
Navigate between them as if they were a single application: Thanks to Next.js's client-side routing, users can move between zones without full page reloads, providing a smooth, SPA-like experience.

However, it's important to understand how resources are managed in a Multi Zones setup:

Separate Bundles: Each zone (application) has its own JavaScript bundle, CSS, and other assets. They are not automatically shared or optimized across zones.
Independent Loading: When a user navigates from one zone to another, the resources for the new zone are loaded independently. This means that common libraries (like React) might be downloaded again if they're used in both zones.
No Automatic Deduplication: Unlike a single Next.js application, Multi Zones doesn't automatically deduplicate shared dependencies across zones. Each zone loads its resources independently.
Zone-Specific Optimization: Performance optimization happens within each zone independently. This includes features like code splitting and lazy loading, but these optimizations don't extend across zone boundaries.

Progressive Enhancement

One of the key benefits of Multi Zones is that it works with progressive enhancement. Even if JavaScript fails to load, users can still navigate between zones using standard HTML links. This is because:

Server-side rendering: Each zone can render its content on the server, ensuring that users see content even without JavaScript.
HTML-based routing: The rewrite rules we set up work at the server level, allowing for navigation between zones even without client-side JavaScript.
Graceful degradation: While features like client-side navigation enhance the experience, the basic functionality of moving between zones remains intact without them.

Conclusion

Next.js Multi Zones offers a powerful solution for building scalable micro-frontends. It allows teams to work independently while maintaining a seamless user experience for end-users. By enabling separate development and deployment and supporting progressive enhancement, Multi Zones provides a robust foundation for large-scale web applications.

However, it's important to understand that Multi Zones involves managing separate applications, each with its own resources. This requires careful planning and consideration of performance implications, especially when it comes to shared dependencies and overall user experience.

As your application grows, consider leveraging Multi Zones to keep your development process efficient and your user experience smooth. Remember, the web is a platform. Multi Zones helps us work with it, not against it, providing a solid foundation for large-scale web applications that can evolve and scale with your needs, while requiring thoughtful architecture and resource management.

Upcoming events

The Test Automation Meetup
PLEASE RSVP SO THAT WE KNOW HOW MUCH FOOD WE WILL NEED Test automation is a cornerstone of effective software development. It's about creating robust, predictable test suites that enhance quality and reliability. By diving into automation, you're architecting systems that ensure consistency and catch issues early. This expertise not only improves the development process but also broadens your skillset, making you a more versatile team member. Whether you're a developer looking to enhance your testing skills or a QA professional aiming to dive deeper into automation, RSVP for an evening of learning, delicious food, and the fusion of coding and quality assurance! 🚀🚀 18:00 – 🚪 Doors open to the public 18:15 – 🍕 Let’s eat 19:00 – 📢 First round of Talks 19:45 – 🍹 Small break 20:00 – 📢 Second round of Talks 20:45 – 🍻 Drinks 21:00 – 🙋‍♀️ See you next time? First Round of Talks: The Power of Cross-browser Component Testing - Clarke Verdel, SR. Front-end Developer at iO How can you use Component Testing to ensure consistency cross-browser? Second Round of Talks: Omg who wrote this **** code!? - Erwin Heitzman, SR. Test Automation Engineer at Rabobank How can tests help you and your team? Beyond the Unit Test - Christian Würthner, SR. Android Developer at iO How can you do advanced automated testing for, for instance, biometrics? RSVP now to secure your spot, and let's explore the fascinating world of test automation together!
December 11 | Coven of Wisdom - Amsterdam
Go to page for The Test Automation Meetup
Coven of Wisdom - Herentals - Winter `24 edition
Worstelen jij en je team met automated testing en performance? Kom naar onze meetup waar ervaren sprekers hun inzichten en ervaringen delen over het bouwen van robuuste en efficiënte applicaties. Schrijf je in voor een avond vol kennis, heerlijk eten en een mix van creativiteit en technologie! 🚀 18:00 – 🚪 Deuren open 18:15 – 🍕 Food & drinks 19:00 – 📢 Talk 1 20:00 – 🍹 Kleine pauze 20:15 – 📢 Talk 2 21:00 – 🙋‍♀️ Drinks 22:00 – 🍻 Tot de volgende keer? Tijdens deze meetup gaan we dieper in op automated testing en performance. Onze sprekers delen heel wat praktische inzichten en ervaringen. Ze vertellen je hoe je effectieve geautomatiseerde tests kunt schrijven en onderhouden, en hoe je de prestaties van je applicatie kunt optimaliseren. Houd onze updates in de gaten voor meer informatie over de sprekers en hun specifieke onderwerpen. Over iO Wij zijn iO: een groeiend team van experts die end-to-end-diensten aanbieden voor communicatie en digitale transformatie. We denken groot en werken lokaal. Aan strategie, creatie, content, marketing en technologie. In nauwe samenwerking met onze klanten om hun merken te versterken, hun digitale systemen te verbeteren en hun toekomstbestendige groei veilig te stellen. We helpen klanten niet alleen hun zakelijke doelen te bereiken. Samen verkennen en benutten we de eindeloze mogelijkheden die markten in constante verandering bieden. De springplank voor die visie is talent. Onze campus is onze broedplaats voor innovatie, die een omgeving creëert die talent de ruimte en stimulans geeft die het nodig heeft om te ontkiemen, te ontwikkelen en te floreren. Want werken aan de infinite opportunities van morgen, dat doen we vandaag.
December 12 | Coven of Wisdom Herentals
Go to page for Coven of Wisdom - Herentals - Winter `24 edition
Mastering Event-Driven Design
PLEASE RSVP SO THAT WE KNOW HOW MUCH FOOD WE WILL NEED Are you and your team struggling with event-driven microservices? Join us for a meetup with Mehmet Akif Tütüncü, a senior software engineer, who has given multiple great talks so far and Allard Buijze founder of CTO and founder of AxonIQ, who built the fundaments of the Axon Framework. RSVP for an evening of learning, delicious food, and the fusion of creativity and tech! 🚀 18:00 – 🚪 Doors open to the public 18:15 – 🍕 Let’s eat 19:00 – 📢 Getting Your Axe On Event Sourcing with Axon Framework 20:00 – 🍹 Small break 20:15 – 📢 Event-Driven Microservices - Beyond the Fairy Tale 21:00 – 🙋‍♀️ drinks 22:00 – 🍻 See you next time? Details: Getting Your Axe On - Event Sourcing with Axon Framework In this presentation, we will explore the basics of event-driven architecture using Axon Framework. We'll start by explaining key concepts such as Event Sourcing and Command Query Responsibility Segregation (CQRS), and how they can improve the scalability and maintainability of modern applications. You will learn what Axon Framework is, how it simplifies implementing these patterns, and see hands-on examples of setting up a project with Axon Framework and Spring Boot. Whether you are new to these concepts or looking to understand them more, this session will provide practical insights and tools to help you build resilient and efficient applications. Event-Driven Microservices - Beyond the Fairy Tale Our applications need to be faster, better, bigger, smarter, and more enjoyable to meet our demanding end-users needs. In recent years, the way we build, run, and operate our software has changed significantly. We use scalable platforms to deploy and manage our applications. Instead of big monolithic deployment applications, we now deploy small, functionally consistent components as microservices. Problem. Solved. Right? Unfortunately, for most of us, microservices, and especially their event-driven variants, do not deliver on the beautiful, fairy-tale-like promises that surround them.In this session, Allard will share a different take on microservices. We will see that not much has changed in how we build software, which is why so many “microservices projects” fail nowadays. What lessons can we learn from concepts like DDD, CQRS, and Event Sourcing to help manage the complexity of our systems? He will also show how message-driven communication allows us to focus on finding the boundaries of functionally cohesive components, which we can evolve into microservices should the need arise.
September 19 | Coven of Wisdom - Utrecht
Go to page for Mastering Event-Driven Design

Building Scalable Micro-Frontends with Next.js Multi Zones

The challenge of growing applications

How can Next.js Multi Zones help?

Setting up a Multi Zones

The reality of Multi Zones

Progressive Enhancement

Conclusion

Upcoming events

The Test Automation Meetup

Coven of Wisdom - Herentals - Winter `24 edition

Mastering Event-Driven Design

Share

Jobs

Senior Web Developer

Lead Developer

Shopware Developer

.Net Developer

View all jobs