In this episode of Micro-Frontends in the Trenches, Luca Mezzalira sits down with Peter Eijgermans to unpack a five-year journey building Spoorviewer, the real-time dashboard powering operations at the Dutch Railways (NS / ProRail).

Peter walks through how four teams modernized a slowing Angular monolith into a dashboard-style shell hosting five remote applications, loaded dynamically at runtime via Module Federation. You'll hear what worked, what didn't, and why the first attempt with Web Components (Custom Elements) failed to deliver on performance.

CHAPTERS

00:00 Cold open: shipping without fear

01:26 Welcome and introductions

03:02 Meet Peter: full-stack, real-time data, and OIDC

05:16 Spoorviewer: a dashboard, not a page-based app

07:22 The five remote apps: Spoorzicht, Plan, Baanvak, Track Occupancy, Maintenance

10:34 Why micro-frontends? The organizational and technical breaking point

12:47 The performance trap of Custom Elements

14:54 Switching to Module Federation: Lighthouse 30 → 75

16:50 Domain-Driven Design and identifying overlapping boundaries

20:11 Recap: shell, lazy loading, DDD, and team independence

23:30 WebSockets aligned to bounded contexts

26:46 How developers felt about the move to micro-frontends

28:11 Guardrails: framework alignment, versioning, shared libraries

31:14 From client-side OIDC to a Backend-for-Frontend "Lego brick"

34:27 Drawbacks and lessons learned along the way

36:41 Architecture surfaces friction, it doesn't create it

39:17 AI on the horizon: predicting train delays

40:39 AI in the developer workflow

42:31 Closing reflections: start with good design

43:21 Wrap-up and outro

Modern Angular ebook by Manfred Steyer: https://payhip.com/AngularArchitectssubscribe to the MFEs newsletter: https://www.buildingmicrofrontends.comIn this episode, host Luca sits down with Manfred Steyer — Angular GDE, trainer, consultant, and creator of Native Federation — to explore the world of micro frontends in the Angular ecosystem.They cover:How popular micro frontends are in the Angular community and when they actually make senseThe different approaches to implementing micro frontends in Angular (hyperlinks, hydration, Module Federation)State management and communication between micro frontends using signals and subjectsHandling multiple Angular versions across a distributed systemHow and why Manfred created Native Federation as a build-tool-agnostic alternative to Webpack Module FederationHow import maps and ES modules power Native Federation under the hoodMigrating from a monolith to micro frontends — key questions to ask before you startThe relationship between the Angular team and Native FederationTop 3 recommendations for developers getting started with micro frontends

“We adopted micro-frontends… and suddenly authentication became everyone’s problem.”

That sentence alone has probably cost teams months of rework, endless Slack threads, and architecture diagrams that aged badly after the first production incident.

In the latest episode of Micro-Frontends in the Trenches, I sit down with Chris Fryer to unpack the realities behind his #microfrontends Framework, the evolving Module Federation ecosystem, and much more

☢️ WARNING: This is not a theoretical conversation.

Listen to the episode and let me know what challenged your perspective the most.

In this episode, I’m joined by Boris Besemer from Vercel to unpack what it really takes to start a migration to micro-frontends without turning it into a never-ending transformation.

We focus on the very first steps teams should take: how to identify the right starting point and how to avoid the most common early mistakes that slow teams down or create unnecessary complexity.

A big part of the conversation explores how the Vercel platform can simplify platform engineering during a migration.

We discuss how tooling, deployment workflows, preview environments, and developer experience can reduce cognitive load while multiple teams progressively move toward a micro-frontend architecture.

I don't think you need to know more than the name of the guest to love this episode: Sam Newman, author of Building Microservices and other best sellers on distributed systems.

This is an episode you don't want to miss where I talk about micro-frontends with Sam drawing parallelisms between the 2 layers of a distributed system.

Enjoy this fantastic episode

===================================

My gear: https://www.amazon.co.uk/shop/my50cents?ref_=cm_sw_r_cp_ud_aipsfshop_W744H9NEJG7C9T3JMFC2Spotify: https://open.spotify.com/show/0W5YEY5T3ApuYS8H9I3DzL?si=c279c2df086b4d8fTwitter: https://twitter.com/lucamezzaliraLinkedIn: https://www.linkedin.com/in/lucamezzaliraInstagram: https://instagram.com/mezzalabTikTok: https://www.tiktok.com/@lucamezzalira

In this episode of Micro-Frontends in the Trenches, I talk with Jeremy Colin (ex-Zalando) about the journey that led to Tailor.js and later Mosaic, two pioneering frameworks that shaped how micro-frontends are built at scale.Jeremy shares the technical challenges, trade-offs, and lessons learned while building these platforms, and why platform engineering is essential for making micro-frontends practical in real-world organizations.We dive into:- The story behind Tailor.js and its role in Zalando’s architecture.- How Mosaic evolved and why it mattered.- The hidden complexities of adopting micro-frontends.- Why platform engineering is key to simplifying and sustaining the practice.I highly encourage all of you to listen to this episode that is part of the micro-frontend history!

We’ve been cooking something new—Remote Components.Imagine pushing a tiny change to your e-commerce site like updating a free shipping banner and having to wait hours for the entire site to build and test. That’s the reality of traditional monolithic frontends, where even the smallest updates can ripple across the codebase, slowing teams down and widening the blast radius for potential problems.Vercel is changing the game with micro-frontends providing an unmatched developer experience so farIn this episode you’ll learn how Vercel micro-frontends implementation can:- Speed up build and deploy times- Reduce risks when releasing features- Empower teams to ship independently without stepping on each other’s toes

More information at: https://vercel.com/microfrontends

In this can't-miss episode, Zack takes us behind the scenes of Module Federation's inception and its game-changing impact on micro-frontend architecture. But that's just the beginning! We dive deep into Zack's current adventures at ByteDance, where Module Federation is being pushed to mind-blowing scales you won't believe. Get ready for some serious tech excitement as we unpack the freshly released Module Federation 2.0. Zack breaks down the new features like the possibility to use Module Federation across multiple bundlers. But wait, there's more! We tackle the elephant in the room - Module Federation and Next.js. Zack shares the challenges of maintaining support for this popular framework and the tough decision to shift gears. Don't worry though, he's got plans to make Module Federation available across the JavaScript ecosystem! What about the future? What mind-bending innovations does Zack have up his sleeve? Also this part is present in this episode! Module Federation website: https://module-federation.io =================================== Follow me for more tips! Spotify: https://open.spotify.com/show/0W5YEY5T3ApuYS8H9I3DzL?si=c279c2df086b4d8f Twitter: https://twitter.com/lucamezzalira LinkedIn: https://www.linkedin.com/in/lucamezzalira Instagram: https://instagram.com/mezzalab TikTok: https://www.tiktok.com/@lucamezzalira