Patrick, a friend of mine in the web development industry, recently alerted me to the existence of the micro frontend design pattern, and specifically the mini-Twitter-storm it's generating:
Dan AbramovI don’t understand micro-frontends.03:48 AM - 26 May 2019
Dan AbramovThe problems they’re supposed to solve sound to me like they’re already solved by a good component model. So is this solving an organizational issue rather than technical one? Such as if two teams can’t agree on anything, even shared infra.03:56 AM - 26 May 2019
Not to be partial, there are also many on the other side of the fence arguing for this pattern:
Joel Denning@joelbdenning@dan_abramov I’m a maintainer of @Single_spa, a framework for microfrontends.
They are microservices in the browser. Meaning separately built and deployed frontend apps that can choose their own framework and libs.
The purpose is organizational scaling and avoiding framework lock-in.06:02 AM - 26 May 2019
I sat down with Patrick and we explored this issue in-depth, evaluating both sides of the argument. You can find the whole video attached below:
This is the first episode of Tech Red Pill, a podcast where we talk and share our opinions on pressing issues and the latest news in the technology sector. Please let us know what you think and/or what you would like to see in the future!