Micro Frontends - a strive for fully verticalized systems

Micro Frontends - a strive for fully verticalized systems

Devoxx Ukraine 2019 (Kyiv, Ukraine)

event: https://devoxx.org.ua/
pptx (with animations): https://drive.google.com/open?id=1POg2y9Q09sW8NTwnhsN3C8lkUsYZ97aS

E6c61f085d7aceaf97b7bd00e9195514?s=128

SQUER Solutions

November 23, 2018
Tweet

Transcript

  1. 2.

    @duffleit David Leitner § Technical Expert at 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
  2. 3.

    @duffleit A definition of micro frontends The idea of micro

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

    @duffleit Sam Newman: § small and focused on one thing

    § … to be autonomous § That‘s it WHY we do them? Microservices    !  CVDD HDD/EDD 
  4. 5.

    @duffleit why autonomous? Independent deployments Small interface surface Technology agnostic

    Based on standards Autonomous operations Parallel Development
  5. 12.

    @duffleit DB DB DB DB DB DB DB DB DB

    Independent deployments Autonomous operations Technology agnostic Based on standards Parallel Development Small interface surface
  6. 13.
  7. 15.
  8. 17.

    @duffleit The frontend is … not an implementation detail, it

    is a critical part of a microservice architecture.
  9. 18.

    @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
  10. 21.
  11. 23.

    @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. 25.

    @duffleit What customers expect: 1 Company == 1 Website I

    don‘t want to maintain this UI/UX anymore. 1 Company === 1 Website
  13. 26.

    @duffleit Flavour #1: Reusage Problem frontend platform backend platform Catalogue

    Ordering Payment Shipping hyperlink hyperlink hyperlink Menu Menu Menu
  14. 27.

    @duffleit Flavour #1: Hyperlink Integration Independent deployments Autonomous operations Technology

    agnostic Parallel Development A consistent UI/UX Smooth user interaction Fast loading
  15. 31.

    @duffleit MonoRepo ☑ Simplifies dependency management. ☑ Allows extensive code

    sharing and reuse. package.json Shared resources (assets, components…) repository
  16. 32.

    @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)
  17. 35.

    @duffleit Flavour #3: Server Side Includes or Edge Side Includes

    <html> <body> <!--#include virtual="/header" --> <!--#include virtual="/content?route=shop" --> <!--#include virtual="/sidebar?version=new-products" --> <!--#include virtual="/footer" --> </body> </html>
  18. 36.

    @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)
  19. 38.
  20. 39.

    @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
  21. 41.
  22. 42.

    @duffleit /catalogue /checkout APP SHELL Header Footer A matter of

    modularisation Hyperlink Integration App Shell Integration Metaframework
  23. 43.
  24. 44.

    @duffleit • they are implemented with iframes. • or start

    using web components now. Flavour #5: Technology agnostic
  25. 45.

    @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. 46.

    @duffleit „a consistent UI“ ! CDN – for static files

    " CMS – for static content # A Component Library $ for one framework (version) $ technology agnostic
  27. 49.

    @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
  28. 50.

    @duffleit Compose your perfect MIX Landing Shop Ordering hyperlink hyperlink

    APP SHELL Header Footer <!–- SSIs --> <!--#include … --> <!--#include … -->
  29. 51.

    @duffleit Key-Takeaways KISS: „think twice if a frontend monolith does

    not fit your needs and start with a monolith first approach.“
  30. 52.

    @duffleit Key-Takeaways „Consider the frontend as part of your microservice

    architecture – and solve UI specific problems with UI specific solutions.“
  31. 53.

    @duffleit Key-Takeaways „micro frontends are not a stack or technology

    – everyone who tells you this, wants to sell you something.“
  32. 55.

    @duffleit If you liked this talk – vote for it.

    I’m David Leitner Non-Hype-Train-Activist & Enthusiastic Developer @duffleit