Hi,

For some reason the idea that micro-frontends could profit from the optimizations of Phoenix LiveView does not leave me in peace.

If anyone has been thinking about it, and would like to experiment, or point to an existing blog/talk/repo, that’d be great.

I have a repo with an experiment, and am stuck due to lack of time,

but it has a minimal functionality to play around with already.

Constraints:

• no iframes

• no dependence on OTP app update mechanisms

The imagined architecture:

• Separate, independent teams can build and operate both LiveView UIs with maximum simplicity and deployment flexibility

• The front-end degrades gracefully if micro-front-ends are down

• Optimizations of LiveView can be utilized, trading for some chattiness between the services

Currently:

• 3 independent nodes are connected in a cluster

• the main_app acts as the front-end, serving the main page

• 2 services push rendered partial LiveViews to which the main_app is subscribed, rendering them as they are, within the main view

I naively tried sending the diffs only but failed, presumably, since the services are independent and using the diff

optimizations would require calling functions, available in each separate app only.

I’m sure it can be done better