I've been seeing the topic of "Microfrontends" being talked about on Twitter recently.
If anyone has any experience in it, please explain what it is and why you'd use it.
(Optional): What are the pros and cons?
I've been seeing the topic of "Microfrontends" being talked about on Twitter recently.
If anyone has any experience in it, please explain what it is and why you'd use it.
(Optional): What are the pros and cons?
For further actions, you may consider blocking this person and/or reporting abuse
Oliver Bennet -
Bharat -
Ethan Lee -
Hana Sato -
Top comments (3)
Very interesting, I have heard that MicroFEs has a lot of overhead and quite a few people were against it.
To me, if a component library was built in a good way, then you would be able to extend a single component without worrying too much about breaking everything. That obviously depends on the complexity of the component. (I might have too many expectations from a component library though)
Thanks for the very detailed reply!
In addition to the Neil Green comment. Micro-frontends is also an approach for strangling a monolith application or evolving it using a strangler pattern. FE technologies evolve very fast and MFEs enabling steadily migrating an application.
I wrote some months ago how to strangle a PHP application to making it server-side and client-side render views using Vue.js.
medium.com/js-dojo/strangling-a-mo...
True true, instead of refactoring the whole app, you start by converting small components until the whole app is converted. Definitely a good use for MFEs.