Microfrontend revolution, module federation, Webpack 5

Do you have a heavy frontend and a lot of developers are working on it? Does it take many hours to build a new version, deploy, run integration tests? There are questions about whose fault something fell in runtime?

In the backend world, people have long used the "divide and rule" principle and sawed their monoliths into microservices (SOA). Separated responsibility, identified code owners, encapsulated domain knowledge, reduced training time for new hires, accelerated testing times, and set up independent deployments.

In the last 5 years in the world of SPA big companies have thought about this business more than once. You can find hundreds of articles and videos on the Internet about the implementation of microfrontends. But a decent standard in the industry has never been formed. Someone saws "expensive" in-house solutions someone struggles with duplicate libraries and modal windows in zoid, some crutches loading assets in single-spa (CSS, fonts, images).

But Pavel found his dream — module federation in Webpack 5 which allows you to import any external server, where another application is deployed, compiled by Webpack 5. It's simple, just like with jQuery — we pulled up the plugin with CDN, inserted it into the page and it worked.

Pavel will tell and show how module federation works in Webpack 5. And talk about how Zack Jackson and Tobias Koppers have done a titanic job to offer a decent standard for microfrontends.