What is Micro-Frontends(MFEs)?
MFEs — microservices approach for modern web.
What is Micro Frontends?
The idea behind Micro Frontends is to think about a website or web app as a composition of features which are owned by independent teams. Each team has a distinct area of business or mission it cares about and specialises in. A team is cross functional and develops its features end-to-end, from database to user interface.
“An architectural style where independently deliverable frontend applications are composed into a greater whole”
In ThoughtsWorks — Technology Radar May 2020 Techniques, MFEs are in “Adopt” stage.
We’ve seen significant benefits from introducing microservices, which have allowed teams to scale the delivery of independently deployed and maintained services. Unfortunately, we’ve also seen many teams create a front-end monolith — a large, entangled browser application that sits on top of the back-end services — largely neutralizing the benefits of microservices. Micro frontends have continued to gain in popularity since they were first introduced.
- Incremental upgrades
- Multiple teams contribute to the frontend
- Simple & Decoupled codebases
- Development speed should be a constant despite a growing application
- External developers should be able to extend the UI
- Different teams should be able to use their own tooling (Technology Agnostic)
May be you have done Angular vs React vs VueJS but now we talking about — Angular + React +VueJS — how they can work together.
Micro frontends are not perfect for every project. They are a solution for scaling development. If you only have a hand full of developers and communication is no issue the introduction of micro frontends won’t bring much value.
- Increased Payload size
- Environment differences
- Operational and governance complexity
- Works best for big teams (hundreds of developer)
- No global standards of development
Implementation example 1:
You can't perform that action at this time. You signed in with another tab or window. You signed out in another tab or…
Implementation example 2:
micro-frontends-demo has 5 repositories available. Follow their code on GitHub.
Join the chat on Slack Donate to this project Build micro frontends that coexist and can ( but don't need to) be…
Build micro frontends that coexist and can (but don’t need to) be written with their own framework. This allows you to:
- Use multiple frameworks on the same page without refreshing the page (React, AngularJS, Angular, Ember, or whatever you’re using)
- Write new code, possibly with a new framework, without rewriting your existing app
- Lazy load code for improved initial load time.
Micro frontends are indeed quite popular in the e-commerce sector. In 2012 the Otto Group, a Germany based mail order company and one of the world’s largest e-commerce players started to split up its monolith. The Swedish furniture company IKEA and Zalando, one of Europes biggest fashion retailers, moved to this model. Thalia, a German bookstore chain, rebuilt its e-reader store into vertical slices to increase development speed.
But micro frontends are also used in other industries. Spotify organizes itself in autonomous end-to-end teams they call Squads. Canopy, an American tax software startup and the sports streaming service DAZN use micro frontends to build its applications.
Microfrontends are sections of your UI, often consisting of dozens of components, that use frameworks like React, Vue, and Angular to render their components. Each microfrontend can be managed by a different team and may be implemented using its own framework. It is practical and suggested to use just one framework for all your microfrontends, although you may add additional frameworks when migrating or when experimenting.
We see it as a proven approach that we should be using when it makes sense to do so.
Got curious — more information,
6 Patterns for Microfrontends
An overview of microfrontend patterns: advantages, drawbacks and implementation.