You have multiple teams working on the same website, and you're having trouble moving forward together, to achieve and maintain good web performance and a satisfying uptime rate.
If so, micro front-end architecture is an approach you should seriously consider! Imagine your website divided into a multitude of fragments like a puzzle, making your teams autonomous and independent.
7 years after moving to a micro-frontend architecture and migrating 6 of our e-commerce sites internationally, and after having created a dozen multi-technology web applications and portals, we'd like to give you some feedback on this architecture.
- What is a micro-frontend? Mono or multi-technology? Mono or multi-technology?
- What kind of infrastructure is needed to support hundreds of prod deployments per month?
- What is the impact on user experience, web performance, and high availability?
- How can we reduce the client-side carbon footprint and reduce the load on an infrastructure that is exploding in the number of micro-applications?
- How can you incrementally overhaul a legacy site without freezing your functional evolution?
- What impact will this have on team organization? Should we expect reluctance?
Time-to-market, performance and resilience have guided our decisions and made this architecture an obvious choice. With concrete examples, we invite you to immerse yourself in the world of micro-frontends.
or sign up with email →
Create a custom schedule.
Take it with you on mobile.
Get listed in the directory.
