Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Micro Frontends - Devops POV

Avi Tzurel
October 25, 2017
55

Micro Frontends - Devops POV

Avi Tzurel

October 25, 2017
Tweet

Transcript

  1. Application Templates - Most presentation pitch you Angular and React

    together. Don't do that - Application should look *The same* - Templates for actions/components/css - src/lib for extraction candidates - Internal libraries - Decision on libs - Axios vs Fetch - Css next vs SCSS App X should *feel* like App Y
  2. CI config - All application should have the same CI

    configuration. - npm run build:prod - npm start - npm run lint - etc...
  3. Nginx / Web server - /configs/{}.json proxies to local configuration

    files - Application configuration should be dynamic. Applications are promoted through environments transparently. - Caching of JS/CSS images etc..
  4. Modules loading - Whatever you choose should be consistent. -

    You can choose a manifest and load JS files from endpoints of have iframes that will use native history. - Loading of modules should be fail- safe. No app should bring the system down
  5. Releases - Releasing an application should be as easy as

    building on CI and having a ready-made module - You can promote/remove from the manifest at any given time.