Skip to main content
Version: 13.x (Current)

Microfrontend Composer architecture

Given their remarkable degree of flexibility, frontend applications are usually composed of multiple moving parts that interacts with each other and with external systems.

The following sections are intended to give the reader a general idea of the actors involved and their connections.

How Microfrontend Composer is served


Being composed at runtime, Mia-Platform Microfrontend Composer needs a couple of configuration files to build your frontend application. These files can be easily generated using the low-code/no-code configurator provided by the Console, and then served through a microservice called Middleware that acts both as web server and configurations provider for the Microfrontend Composer.

The service can be easily deployed using one of two marketplace applications:

How Microfrontend Composer works at runtime

At runtime the Microfrontend Composer uses the configuration files to structure the desired frontend application, which in turn needs to fetch resources and create connections to populate its pages.

Page composition

In pages composed by Web Components the custom elements have to be sourced remotely, for example from a CDN or a web server. Either way, the components are used by the underlying engine (i.e., micro-lc) to build the pages following the blueprints provided by configuration files.

In turn, on the page, the components may need to communicate with a backend. While back-kit tends to centralize this functionality on clients components, each component is independent in performing HTTP requests to external systems.