🚀 Special online meetup with two contributors form the Native Federation Team about amazing new Features in v4
Build Performance, Native Federation Under the Hood
by Auke van Oostenbrugge,
Native Federation Project Lead
Build Performance, Native Federation Under the Hood
by Alejandro Ramírez Jiménez,
Native Federation Advisory Board Member
Seeing the Negotiation: DevTools for Native Federation
by Lutz Leonhardt,
Native Federation Advisory Board Member
8<--
Session Details:
Dependency Sharing - Native Federation Under the Hood
by Auke van Oostenbrugge
When using native-federation, you expect the runtime to always choose the most efficient combination of shared dependencies without breaking your decentralized app in the browser. But how does the runtime know what version of each dependency to choose? And does "the best combination" exists? What levers can you pull to optimize your micro frontend architecture? In this presentation I'll provide a small peek under the hood and show the negotiation process that native-federation goes through to make sure your web application will perform.
Build Performance, Native Federation Under the Hood
by Alejandro Ramírez Jiménez
Micro frontends live or die by their runtime, but the place developers actually spend their day is the inner loop: that wait after hitting save. So what happens between saving a file and seeing the change in the browser? Why was that wait several seconds long, and how did Native Federation v4 turn it into near‑instant feedback? In this talk I'll open up the build side of native‑federation: the steps it runs on every change, what v4 now skips, and what it caches to avoid redoing work. I'll back it with real numbers from migrating a production micro frontend to v4, where warm rebuilds dropped by roughly 92% (about 12× faster)
Seeing the Negotiation: DevTools for Native Federation
by Lutz Leonhardt
Native Federation resolves shared dependencies at startup: it negotiates the declarations of every remote down to a set of actual downloads and writes the result into an import map. It's a lot of work done for you — and once the page has booted, the reasoning behind it isn't easy to reconstruct.
This talk introduces a read-only Chrome DevTools extension that reads the negotiation back out of a running application: which versions were shared, scoped or skipped, who provides each mapped file, and which chunks sit behind it. We'll walk through real cases — a strict share scope, a version split across remotes, and a host running Angular, React and Svelte side by side — and see exactly what the resolver decided, and why.
Speakers:
Auke van Oostenbrugge
Native Federation Project Lead
Native Federation maintainer, MSc in Advanced Software Development, and Frontend R&D Software Engineer at ParnasSys. Drives the daily development and evolution of the Native Federation ecosystem.
Lutz Leonhardt
Native Federation Advisory Board Member
Lutz Leonhardt is an independent consultant from Dresden, Germany, with 18+ years in enterprise software. He led Siemens' Angular micro frontend migration from Module Federation to Native Federation across 15 teams, and now serves as an Industry Advisor on the Native Federation Advisory Board. He has a weakness for systems whose behaviour is hard to observe — and for building the tools that make them observable.
Alejandro Ramirez Jimenez
Native Federation Advisory Board Member
Worked with Module Federation and Native Federation for 4+ years across large healthcare and banking projects at Sanitas and Santander.
