4 ms·
I was working somewhere earlier this year that was thinking about going into micro frontends. To me the frameworks seemed pretty immature. I had perhaps naive
by darepublic 3y ago
I was working somewhere earlier this year that was thinking about going into micro frontends. To me the frameworks seemed pretty immature. I had perhaps naively thought when I first heard about micro frontends that they would be a bunch of iframes that you could compose together on a page, each with its own data fetching logic and thus reuse stuff that was otherwise totally disparate. But someone pointed out some practical difficulties of doing this and I agree it would be quite tough to pull off. It seemed like micro frontends just were trying to get the benefits of a monorepo but with everything in separate repos. And then having some complicated build logic so that hypothetical team could be working in angular 2 and hypothetical team b could be working in react and they could harmoniously mingle their work, in page divided blocks. i.e. at least as it was proposed where I was you couldn't mix and match components on a page, it was just 'route a will use one micro fe, route b will be another'. I'm wondering is this how micro fe is actually done? To me it seems pretty hackneyed and basic, not to mention if you wanted to do this monorepo would be more suitable.