Micro Frontends Beyond the Buzzword!

Micro Frontends Beyond the Buzzword!

E6c61f085d7aceaf97b7bd00e9195514?s=128

SQUER Solutions

April 18, 2019
Tweet

Transcript

  1. 2.

    @duffleit leitner.io David Leitner ▪ Technical Expert/Lead Developer at Senacor

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

    @duffleit leitner.io “the idea of micro frontends is to extend

    the concept of micro services to the frontend world.”
  3. 4.

    @duffleit leitner.io Disclaimer 1: That's fine in 80 % of

    the cases. SPA API Gateway Microservice Microservice Microservice DB DB DB
  4. 8.

    @duffleit leitner.io Why autonomous? ✔ Independent Deployments ✔ Distinct Operations

    ✔ Technology Agnostic ✔ Model around Business Domains ✔ Small Interface Surface ✔ Parallel development
  5. 9.

    @duffleit leitner.io Microservice API Gateway SPA Microservice Microservice DB DB

    DB ❌ Independent Deployments ❌ Distinct Operations ❌ Technology Agnostic ❌ Small Interface Surface ❌ Model around Business Domains ❌ Parallel development Frontend Monolith
  6. 14.

    @duffleit leitner.io μService Ordering μService DB μService μService DB DB

    Catalogue Profile μService DB DB Hyperlink Hyperlink Approach 1: Hyperlink Integration
  7. 15.

    @duffleit leitner.io ✔ Independent Deployments ✔ Distinct Operations ✔ Technology

    Agnostic ✔ Small Interface Surface ✔ Model around Business Domains ✔ Parallel development Based on the assumption to have fully verticalized systems. μService Ordering μService DB μService μService DB DB Catalogue Profile μService DB DB Hyperlink Hyperlink Approach 1: Hyperlink Integration
  8. 16.

    @duffleit leitner.io μService Ordering μService DB μService μService DB DB

    Catalogue Profile μService DB DB Hyperlink Hyperlink Dashboard Hyperlink μService DB ⛔ Overfetching ⛔ Overrequesting Approach 1: Hyperlink Integration
  9. 17.

    @duffleit leitner.io Approach 1: Hyperlink Integration with Backend for Frontends

    μService Ordering μService DB μService μService DB DB Catalogue Profile μService DB DB Hyperlink Hyperlink Dashboard Hyperlink μService DB BFF Service BFF Service BFF Service BFF Service https://samnewman.io/patterns/architectural/bff/ Presentation Process Flow Domain Logic Data Presentation Process Flow Domain Logic Data
  10. 18.

    @duffleit leitner.io Approach 1: Hyperlink Integration with GraphQL μService Ordering

    μService DB μService μService DB DB Catalogue Profile μService DB DB Hyperlink Hyperlink Dashboard Hyperlink μService DB GraphQL https://samnewman.io/patterns/architectural/bff/ Presentation Process Flow Domain Logic Data
  11. 23.

    @duffleit leitner.io μService Ordering μService DB μService μService DB DB

    Catalogue Profile μService DB DB Hyperlink Hyperlink Dashboard Hyperlink μService DB View Aggregation Layer Horizontal Layer
  12. 24.

    @duffleit leitner.io μService Ordering μService DB μService μService DB DB

    Catalogue Profile μService DB DB Hyperlink Hyperlink Dashboard Hyperlink μService DB View Aggregation Layer Horizontal Layer
  13. 25.

    @duffleit leitner.io Dashboard Profile Profile μService DB Catalogue μService DB

    Catalogue Ordering Ordering μService DB Dashboard μService DB
  14. 26.

    @duffleit leitner.io Dashboard Profile Catalogue Ordering Ordering Catalogue Hyperlink Hyperlink

    Dashboard How to slice? One “Micro Frontend” per page. 2...n Micro Frontends per page.
  15. 28.

    @duffleit leitner.io Repository Build & Deploy Server Browser Composed Application

    Micro Frontend Build Time Integration Server Side Integration Runtime Integration
  16. 29.

    @duffleit leitner.io Repository Build & Deploy Server Browser Mono Repo

    package.json Composed Application Micro Frontend Build Time Integration MonoRepo ✔ Simplifies Dependency Management. ✔ Allows extensive code sharing and reuse. Angular Workspaces
  17. 30.

    @duffleit leitner.io Repository Build & Deploy Server Browser Composed Application

    Micro Frontend Build Time Integration ❌ Independent Deployments ❌ Distinct Operations ❌ Technology Agnostic ✔ Small Interface Surface ✔ Model around Business Domains ✔ Parallel development
  18. 31.

    @duffleit leitner.io Repository Build & Deploy Server Browser Composed Application

    Micro Frontend Server Side Integration Project Mosaic
  19. 32.

    @duffleit leitner.io Based on the concept of Server Side Includes

    or Edge Side Includes ⛔ JS and CSS global scoped ⛔ Round-Trips are needed
  20. 33.

    @duffleit leitner.io Tailor is a Layout Server header fragment μService

    account fragment μService catalogue fragment μService maps your request to a template checkout-template.html ... dashboard.template.html profile-template.html
  21. 35.

    @duffleit leitner.io supports Javascript-Isolation account fragment μService html script styles

    1...n init(fragment-dom){ ... } isolate CSS: naming-convention like BEM
  22. 36.

    @duffleit leitner.io Repository Build & Deploy Server Browser Composed Application

    Micro Frontend Server Side Integration ✔ Independent Deployments ✔ Distinct Operations ✔ Technology Agnostic ✔ Small Interface Surface ✔ Model around Business Domains ✔ Parallel development
  23. 37.

    @duffleit leitner.io Repository Build & Deploy Server Browser Composed Application

    Micro Frontend Runtime Integration Aggregating UI Routing, Templates, Lazy Loading
  24. 40.

    @duffleit leitner.io the aggregation and configuration is done on a

    single point. immutablewebapps.org index.html https://12factor.net/
  25. 41.

    @duffleit leitner.io Repository Build & Deploy Server Browser Composed Application

    Micro Frontend ✔ Independent Deployments ✔ Distinct Operations ✔ Technology Agnostic ✔ Small Interface Surface ✔ Model around Business Domains ✔ Parallel development Runtime Integration
  26. 43.

    @duffleit leitner.io Server Browser Server Side Integration Runtime Integration Request

    Response Model Interactions between different Verticals are done on the Backend. Longliving App State in the frontend & verticals need to interact with each other.
  27. 45.

    @duffleit leitner.io Most of the state that needs to be

    shared between child applications is just API data. UI-state that isn't in the API is much less commonly shared. Having a shared API cache can be a simple but very efficient solution.
  28. 49.

    @duffleit leitner.io what designers expect us to do how it

    finally looks like what customers would like to see
  29. 50.
  30. 52.

    @duffleit leitner.io SPA-A component library Time Effort 2019 2020 2021

    SPA-B component library SPA-C component library a promise that you will save time in the future by reusage. a dependency between projects.
  31. 54.

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

    Component Libraries Even if something has to look equal, it does not have to be technically the same. Source of truth
  32. 55.

    @duffleit leitner.io 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.
  33. 58.

    @duffleit leitner.io Micro Frontends in a nutshell Integration and Slicing

    Is your application big?* Frontend Monolith no Are UI/Domain Parts strongly independent? yes Applications integrated with Hyperlinks no Server Side Integration no Are Server-Roundtrips a problem? yes Runtime Integration yes * an application is big enough to justify using micro frontends, if slight UI/UX differences between the two most unrelated subpages are acceptable.
  34. 59.

    @duffleit leitner.io Mix and Match Landing Shop Ordering hyperlink hyperlink

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

    @duffleit leitner.io Lots of interactions and state-sharing between your micro

    frontends are an indicator that your micro frontends are too micro.