Today I Learned - Rocky Kev

TIL about Micro-frontends

POSTED ON:

TAGS:

Micro frontends are a new pattern where web application UIs (front ends) are composed from semi-independent fragments that can be built by different teams using different technologies. Micro-frontend architectures resemble back-end architectures where back ends are composed from semi-independent microservices.

via The Strengths and Benefits of Micro Frontends

It's still pretty new, so there's no single dominant implementation and no clear “best” micro-frontend framework.

Using the Island Architecture concept, (more at The Island Architecture in a nutshell):

It'll be three separate apps. You can build all three in Vue, each in it's own framework, or even one in JS, one in WebAssembly, and one in some weird Python-to-JS compiler.

The big unknown?

How will the micro-frameworks talk to each other?

Luca Mezzalira's post has an idea:

In the mental model I created for designing micro-frontends, it’s encouraged to communicate between micro-frontends using a publish-subscribe pattern for enforcing the boundaries between micro-frontends, avoid or at least reduce the design-time coupling that leads to more autonomous teams

So this can be a event bus, or a separate application that watches for states.


Related TILs

Tagged:

TIL how Svelte is different fom Vue/React

TIL about Micro-frontends

Micro frontends are a new pattern where web application UIs (front ends) are composed from semi-independent fragments that can be built by different teams using different technologies.

TIL about Partial Hydration

Partial rehydration is an extension of the idea of progressive rehydration where individual pieces of a server-rendered application are 'booted up' over time. This contrasts with the approach of initializing the entire application at once.