What if you could break up your frontend monolith into independently deployable micro apps? Learn how Webpack 5's Module Federation makes it a reality.
#1about 4 minutes
Understanding the scaling challenges of monolithic applications
A product's growth from a simple feature to a complex system demonstrates how monolithic codebases slow down development and onboarding.
#2about 2 minutes
The architectural evolution from monoliths to micro-frontends
Software architecture has evolved from monoliths to frontend/backend splits and microservices, with micro-frontends being the next logical step for UI complexity.
#3about 5 minutes
Using Webpack 5 Module Federation for micro-frontends
Webpack 5's native Module Federation provides a standardized and widely adopted tool for building micro-frontends, avoiding the niche nature of other frameworks.
#4about 3 minutes
Live demo of a shell app consuming a micro-app
A practical demonstration shows how a shell application dynamically imports and renders a separate micro-app, both locally and from a deployed URL.
#5about 2 minutes
Differentiating micro-frontends from micro-apps
A micro-app combines the frontend focus of a micro-frontend with the backend concerns of a microservice to perform a single, well-defined task.
#6about 5 minutes
Exploring practical use cases for micro-apps
Micro-apps can be used for design system components, team autonomy, gradual migrations, and building a portfolio of applications from shared parts.
#7about 2 minutes
Coordinating shared dependencies and versions
A central platform team or guild should define and enforce exact versions for core shared dependencies like React to ensure consistency across all micro-apps.
#8about 5 minutes
Avoiding common pitfalls with micro-frontends
Key challenges include managing version deployments, handling CORS, ensuring security by avoiding third-party scripts, and implementing proper error boundaries.
#9about 2 minutes
Managing global UI state and communication patterns
Use singleton providers from the shell application for global UI elements like modals and notifications to prevent duplication and maintain control.
#10about 1 minute
Knowing when not to use a micro-frontend architecture
Micro-frontends should only be considered for transactional features or when organizational needs require separate deployment cadences; otherwise, a simple component is better.
#11about 2 minutes
Key takeaways for adopting micro-frontends
Successful adoption relies on using modern tools like Webpack 5, ensuring the architecture fits the organizational structure, and maintaining strong coordination.
Related jobs
Jobs that call for the skills explored in this talk.
Micro Components - a different approach to a simpler component-based webThere has been a lot of heated discussion lately in the web community about component based development. One side argued that Web Components are a standard we should follow whereas others complained that they still lag behind in what frameworks offer...
Why Attend a Developer Event?Modern software engineering moves too fast for documentation alone. Attending a world-class event is about shifting from tactical execution to strategic leadership.
Skill Diversification: Break out of your specific tech stack to see how the industry...