Microfrontends (Webpack Module Federation)
frontendWe've started using it in real projects. The experiments dispelled the biggest fears, and now parts of the UI live as independently deployed modules: a team ships its piece without waiting for a shared build. A nice bonus — the same "cut it into independent pieces" approach we use with microservices on the backend now works across the whole vertical.
Tried it out on experimental setups: a host application plus a couple of remote modules, shared dependencies, independent builds. The pitfalls turned up exactly where I expected — aligning versions of shared libraries and routing between modules — but the concept works: a module is built and shipped on its own, and the host picks it up at runtime.
Got acquainted with microfrontends built on Webpack Module Federation: the application is assembled from independently deployed pieces that exchange modules right at runtime. The idea is tempting — our frontends keep growing, and being able to ship parts of the UI independently of each other looks very attractive. I'm digging into where the pitfalls are.