Micro Frontends - a Strive for fully Verticalized Systems

Micro Frontends - a Strive for fully Verticalized Systems

Voxxed Days Bucharest (Bucharest, Romania)

event: https://romania.voxxeddays.com/

E6c61f085d7aceaf97b7bd00e9195514?s=128

SQUER Solutions

March 22, 2019
Tweet

Transcript

  1. 1.

    leitner.io - @duffleit micro frontends a strive for fully verticalized

    systems_ leitner.io - @duffleit Voxxed Days Bucharest
  2. 3.

    leitner.io - @duffleit David Leitner ▪ Technical Consultant for Senacor

    Technologies ▪ Lecturer for post diploma courses at UAS Technikum Vienna ▪ I do a couple of things around the tech- community I‘m writing code
  3. 4.

    leitner.io - @duffleit A definition of micro frontends The idea

    of micro frontends is to extend the concepts of micro services to the frontend world.
  4. 5.

    leitner.io - @duffleit Sam Newman: ▪ small and focused on

    one thing ▪ … to be autonomous ▪ That‘s it WHY we do them? Microservices * UBERHDTV - https://imgur.com/gallery/nup4lfX CVDD HDD/EDD *
  5. 6.

    leitner.io - @duffleit why autonomous? ✅Independent deployments ✅Small interface surface

    ✅Technology agnostic ✅Based on standards ✅Autonomous operations ✅Parallel Development
  6. 13.

    leitner.io - @duffleit DB DB DB DB DB DB DB

    DB DB Independent deployments Autonomous operations Technology agnostic Based on standards Parallel Development Small interface surface
  7. 18.

    leitner.io - @duffleit The frontend is … not an implementation

    detail, it is a critical part of a microservice architecture.
  8. 19.

    leitner.io - @duffleit frontend platform backend platform Independent deployments Autonomous

    operations Technology agnostic Based on standards Parallel Development Small interface surface a frontend monolith was born a micro frontend TO THE RESCUE Independent deployments Autonomous operations Technology agnostic Based on standards Parallel Development Small interface surface
  9. 23.

    leitner.io - @duffleit Flavour #1: Hyperlink Integration frontend platform backend

    platform Catalogue Ordering Payment Shipping hyperlink hyperlink hyperlink
  10. 24.

    leitner.io - @duffleit Flavour #1: Breaking service boundaries frontend platform

    backend platform Products Ordering Payment Shipping Dash board
  11. 25.

    leitner.io - @duffleit Flavour #1: Backend for Frontend frontend platform

    backend platform Products Ordering Payment Shipping Dash board BFF BFF BFF BFF BFF samnewman.io/patterns/architectural/bff/
  12. 26.

    leitner.io - @duffleit Flavour #1: Backend for Frontend frontend platform

    backend platform Products Ordering Payment GraphQL Shipping Dash board samnewman.io/patterns/architectural/bff/
  13. 29.

    leitner.io - @duffleit Flavour #1: Reusage Problem frontend platform backend

    platform Catalogue Ordering Payment Shipping hyperlink hyperlink hyperlink Navigation Navigation Navigation
  14. 31.

    leitner.io - @duffleit Flavour #1: Hyperlink Integration Independent deployments Autonomous

    operations Technology agnostic Parallel Development A consistent UI/UX Smooth user interaction Fast loading
  15. 34.

    leitner.io - @duffleit Flavour #2: Build Time Integration BUNDLED FRONTED

    UI-Shared-Stuff (e.g. SPA-Framework, Components, Routing) Mono Repo
  16. 35.

    leitner.io - @duffleit MonoRepo Simplifies dependency management. Allows extensive code

    sharing and reuse. package.json Shared resources (assets, components…) repository
  17. 36.

    leitner.io - @duffleit Flavour #2: Build Time Integration Independent deployments

    Autonomous operations Technology agnostic Parallel Development A consistent UI/UX Smooth user interaction Fast loading* BUNDLED FRONTED UI-Shared-Stuff (e.g. SPA-Framework, Components)
  18. 38.

    leitner.io - @duffleit Flavour #3: Transclusion BUNDLED FRONTED UI-Shared-Stuff (e.g.

    SPA-Framework, Components) The bundling is done by the webserver.
  19. 39.

    leitner.io - @duffleit Flavour #3: Server Side Includes or Edge

    Side Includes <html> <body> <!--#include virtual="/products" --> <!--#include virtual="/payments" --> <!--#include virtual="/dashboard" --> <!--#include virtual="/shipping" --> </body> </html>
  20. 40.

    leitner.io - @duffleit Flavour #3: Transclusion Independent deployments Autonomous operations

    Technology agnostic Parallel Development A consistent UI/UX Smooth user interaction Fast loading BUNDLED FRONTED UI-Shared-Stuff (e.g. SPA-Framework, Components)
  21. 42.

    leitner.io - @duffleit Flavour #4: App Shell Integration APP SHELL

    Header Footer The aggregation is done on the client.
  22. 43.

    leitner.io - @duffleit Flavour #4: App Shell Integration Independent deployments

    Autonomous operations Technology agnostic Parallel Development A consistent UI/UX Smooth user interaction Fast loading APP SHELL Header Footer
  23. 45.
  24. 46.

    leitner.io - @duffleit • they are implemented with iframes. •

    or start using web components now. Flavour #5: Technology agnostic
  25. 47.

    leitner.io - @duffleit Flavour #5: Metaframework Metaframework /catalogue /checkout Independent

    deployments Autonomous operations Technology agnostic Parallel Development A consistent UI/UX Smooth user interaction Fast loading
  26. 48.

    leitner.io - @duffleit „a consistent UI“ 1) CDN – for

    static files 2) CMS – for static content 3) A Component Library
  27. 49.

    leitner.io - @duffleit „a component library in code“ SPA-C SPA-B

    SPA-A component library Time Effort 2019 2020 2021 component library component library a promise that you will save time in the future by reusage. you introduce a dependency between your projects. copy & own
  28. 51.

    leitner.io - @duffleit Low Fidelity High Fidelity Design Toolkits Design

    Specifications Source of truth Even if something has to look equal, it does not have to be technically the same. a design system != component library Component Libraries
  29. 52.

    leitner.io - @duffleit „a component library“ If you really need

    a component library, then build it framework agnostic. If Angular can be ignored JSX + CSS Modules worked good for us. And, of course web components.
  30. 53.

    leitner.io - @duffleit Flavour #5: Metaframework Metaframework /catalogue /checkout Independent

    deployments Autonomous operations Technology agnostic Parallel Development A consistent UI/UX Smooth user interaction Fast loading
  31. 55.
  32. 56.

    leitner.io - @duffleit Summarize Approaches /catalogue /checkout APP SHELL Header

    Footer Hyperlink Integration App Shell Integration Metaframework Integration Time Frontend Backend Build Transclusion Build-Time Integration Modularization
  33. 58.

    leitner.io - @duffleit A general decision advice Your application is

    big?* The need for smooth user interaction Build Time Integration Hyperlink Integration Strongly Independent UI/Domain Parts Complex modularisation needed Transclusion App Shell Integration Meta- Framework * an application is big enough to justify using micro frontends, if slight UI/UX differences between the two most unrelated subpages are acceptable. Yes No
  34. 59.

    leitner.io - @duffleit Compose your perfect MIX Landing Shop Ordering

    hyperlink hyperlink APP SHELL Header Footer <!–- SSIs --> <!--#include … --> <!--#include … -->
  35. 60.

    leitner.io - @duffleit Key-Takeaways „Think twice if a frontend monolith

    does not fit your needs and start with a monolith first approach.“
  36. 62.

    leitner.io - @duffleit Key-Takeaways „Consider the frontend as part of

    your microservice architecture – and solve UI specific problems with UI specific solutions.“