- Who does hold the domain?
- Does team response for the whole page or just for a part of it?
- Who is responsible for MFE Infrastructure
- Horizontal or Vertical approach
- Client Side - Templates-like
- Server Side - main question how to put everything together. Parsing templates
- Edge Side - Edge-side includes, "ESI". Served on the edge: Little Article
Webpack Module Federation, Single SPA, TailorX, ILC (Isomorphic Layout Composer). PRIVJS - Microfrontend for NextJS with Module Federation and SSR
- Only one options is available for NextJS which supports module federation and SSR
PRIVJS. Microfrontend for NextJS. ~100$ per month - Good options by default

- Good choise for nodejs and something custom:

- Really good option because of having lots of features out of the box

- Mixing TailorX and Single SPA

- Open Components - works since ~2014

- Piral - quite new.

inspired by this blog : blog.bitsrc.io/how-to-develop-microfrontends
To properly run this application we have to run each of them
- cd cats,
npm start - cd dogs,
npm start(in another console) - cd container,
npm start(in another console)
To run on UNIX instead of npm start just use npm start_unix
This app consists of 3 parts:
Container. It is a root of our entire application. It has MicroFrontend component - special container which wraps and draw our single components Dog and CatCats. SPA which draws cat and button to change a random cat. Along with that our Cat application has routing and after redirecting on "/cat/:greeting" it will show us a cat with greeting message.Dogs. SPA which draws a random dog.
- config-overrides - in order to prevent chunking and do that without webpack configuration ejection we need to
use config-overridesfile +react-app-rewired. Used in Cats and Dogs apps.
