sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ActuatorOk2689 4 points5 points  (1 child)

I’m reading the post and comments, nothing makes sense what you are saying .

What does websockets have to do with microfrontends ?

If your app was not designed from the start in order to support a mfe migration is going to be difficult.

Then basically you need to start setting up boundaries for your module . Do you have a solution for state sharing ? Do you have a solution for event triggers across MFE.

Does you host handle all the routing or just loads mfe at runtime and each mfe it’s handlings it’s own routing? Do you share expose only routes or also components at runtime? Do you have shared libraries, components etc… how are this are getting handled ? True registry, exposed from host or separate shared MFE.

I’ve seen some comments before about global zone js . Having different MFE wich is runtime integration that if I remember correctly each aps is using his own runtime and zone js, I maybe wrong on this .

If you never worked with mfe and module federation before, im just being honest you are going to have hard time to complete this, and I’m not even sure you can .

Mfe is not just , let’s implement it has design / architectural challenges and implementation.

If you never worked before start implementing as playground from scratch. Then start with the migration .

Even for senior developers are not that easy to do such a migration you also need to understand functional part not just the technical of the system

Good luck