...
A shell application which will provide shared dependencies and shared UI elements (like the header and footer)
Two domain applications A guest application which will be lazy loaded into the shell at runtime, using the shell to supply those shared dependencies.
Production bundles from the three two applications will be loaded as static assets onto three two different express servers (using fedx-scripts serve) to simulate a production-like environment.
...
For simple MFEs, we’ll consider the full page load to be the “largest contentful paint” and use the network tab to understand how quickly that happens with various levels of throttling. This will let us understand overall load time regardless of whether we’re using a full page load (current MFEs) or progressive loading (composed MFEs) of content. Loading a domain MFE into the shell after the shell has loaded is considered ‘equivalent’ to loading a current MFE via a full page load for all but the first MFE loaded.
To compare the load time of the guest MFE with that of traditional MFEs, we’ll measure: 1) the time it takes for the host/guest to load vs 2) the combined time of loading the host MFE as a “traditional” MFE, plus the time it takes the guest to load as a “traditional” MFE, simulating a user clicking between the two experiences and getting a full page refresh on the guest MFE.