From Google vikerman say ： Micro front end use cases are real ：AdWords It's the biggest micro front end project I've ever seen , There are dozens of them 100 Developers use the same “ product ”, But they have their own release cycle . Of course, there are some problems to be solved .
Opinions vary ：
Imagine a world ,[DB] - > MicroServices Microservices - > Microfrontend Each layer of micro front end has its own development cycle ！
We from asp / jsp Page goes to SPA, Because we don't want to load the full... On every request html / js And only load the data ,Microfrontends It looks like it's back to a certain point ...... Or I don't understand the concept correctly
In my submission microfrontend It doesn't necessarily mean reloading every page . in my opinion , This mainly means that multiple teams build and deliver independently of each other SPA Part of . All this shows , First of all, you need to have at least dozens of team size thresholds .
I see this even used by a small team just because it sounds strange ......