Micro Frontends

As a frontend team leader, one of your most crucial responsibilities is ensuring your team remains adaptable and forward-thinking in an ever-evolving technological landscape. While standardizing on a single framework can provide short-term efficiency, it risks limiting your team’s growth and flexibility in the long run. Let’s explore strategies to avoid this pitfall, complete with real-world examples. Focus on Core Principles At the heart of frontend development lie the fundamental web technologies: HTML, CSS, and JavaScript. These form the bedrock upon which all frameworks are built. By emphasizing mastery of these core technologies, you equip your team with transferable skills that transcend any single framework. ...

Managing multiple Angular projects can be a daunting task, especially as teams grow and codebases become more complex. In this article, we’ll explore three common approaches for managing multiple Angular projects: Micro Frontends, Monorepo, and Reusable Shared Module. We’ll compare their advantages, disadvantages, and suitability for different scenarios to help you make an informed decision for your Angular projects. Micro Frontends Consider a large e-commerce platform comprising several distinct sections, including product catalog, shopping cart, checkout, and user profile. With micro frontends, each section can be developed and deployed independently as a separate micro frontend. This enables different teams to work autonomously on their respective sections, improving development speed, scalability, and flexibility. ...

This is the companion for Why and How. It proves one thing: a host page can load separately built Angular and React bundles as custom elements, pass a message attribute down, and take a microfrontend:message event back. It does not prove Module Federation, independent production deploys, or a shared design system. npm run dev builds the remotes, then starts one Qwik server that serves them from public/mfes/. Rust WebAssembly is a shell helper for CPU work, not a fourth micro frontend. ...

Once you have a reason to split the UI, the next decision is how the pieces become one page. That assembly step is composition: the host application — the shell — decides where each slice renders and what it is allowed to see. There are a few honest ways to do it. I picked one for the companion: the browser loads separately built bundles and mounts them as custom elements — HTML tags the host did not compile. That is client-side composition. It is not the only option, and it is not a production platform by itself. ...

A micro frontend is a slice of a web UI that one team can build, test, and ship without waiting on the rest of the page. Picture two teams and two pipelines on one checkout: catalog can go out on Tuesday while payments is still in review. That independence is the whole reason to do this. It is also the cost. Someone still has to own the page those slices land on, and someone has to keep the agreement between them from rotting. ...