Sustainable Client Architectures with Micro Apps

@ManfredSteyer Sustainable Client Architectures with Micro Apps Manfred Steyer SOFTWAREarchitect.io
ManfredSteyer

@ManfredSteyer About me… • Manfred Steyer • SOFTWAREarchitect.io • Angular
Trainings and Consultancy • Google Developer Expert (GDE) Page ▪ 4 Manfred Steyer Public and In-House http://softwarearchitect.io/workshops

@ManfredSteyer ✓ Commodore 64 ✓ 1982 ✓ ~ 1 MHz
✓ 64 KB RAM ✓ Disks with 170 KB

@ManfredSteyer Version with two cores ;-) Challenge: Resources!

@ManfredSteyer Challenges today: Complexity

@ManfredSteyer Coordination b/w teams

@ManfredSteyer Long Time Maintain- ability Maintain + Extend for 10+
yrs

@ManfredSteyer There are milk products lasting longer than some JavaScript
frameworks

@ManfredSteyer Contents 1) Micro Apps with JavaScript 2) DEMO 3)
Recipes 4) Evaluation

@ManfredSteyer 1) Micro Apps with JavaScript

@ManfredSteyer Idea System Team A Team B Framework Architecture Maintainability?
Hard to change!

@ManfredSteyer Idea µService µService µService

@ManfredSteyer Idea µApp µApp µApp

@ManfredSteyer Folie▪ 16 Pro Contra

@ManfredSteyer UI Composition w/ Hyperlinks µApp SPA µApp SPA µApp
SPA <a href="…>…</a> <a href="…>…</a>

@ManfredSteyer ✓ Simple  Loosing State  Load a new
Application  Consistent Look and Feel

@ManfredSteyer

@ManfredSteyer Web Components for Shared Widgets?

@ManfredSteyer Framework independent Components

@ManfredSteyer Can be pollyfilled down to IE11

@ManfredSteyer µService Providing a (SPA based) Shell µApp µApp µApp
Shell ▪ iframes ▪ Bootstrapping several SPAs ▪ Consider Lazy Loading!

@ManfredSteyer Common Interface for µApps • Shell should not know
details of µApp and used Frameworks! • µApp provides events • µApp consumes events • Wrap µApp as Web Component?

@ManfredSteyer 2) DEMO

@ManfredSteyer µService µApp3 µApp2 µApp1 Shell Web Components for Shell-Architecture
Shared Widget Shared Widget Shared Widget Web Components for shared Widgets

@ManfredSteyer 3) Recipes

@ManfredSteyer Communication

@ManfredSteyer Communication b/w Web Components <client-a state="appState" message="handle(event)"></client-a> <client-b state="appState"
message="handle(event)"></client-b> JavaScript in Shell

@ManfredSteyer Routing

@ManfredSteyer Routing /client-a/this/that /client-b/this/that /client-c/this/that :

@ManfredSteyer Lazy Loading

@ManfredSteyer Lazy Loading const content = document.getElementById('content');

@ManfredSteyer Lazy Loading const content = document.getElementById('content'); // Add script-Tag
const script = document.createElement('script'); script.src = [...]; content.appendChild(script);

@ManfredSteyer Lazy Loading const content = document.getElementById('content'); // Add script-Tag
const script = document.createElement('script'); script.src = [...]; content.appendChild(script); // Add Element const element: HTMLElement = document.createElement('client-a'); element.addEventListener('message', (event) => [...]); element.setAttribute('appState', [...]); content.appendChild(element);

@ManfredSteyer Bundling

@ManfredSteyer Bundles Custom Element 1 Custom Element 2 Custom Element
3 Libraries: Angular, Bootstrap, … Libraries: Angular, Bootstrap, …

@ManfredSteyer Compiling down to JavaScript (more or less) e. g.
w/ Stencil, Angular Ivy Custom Element 1 Custom Element 2 Custom Element 3

@ManfredSteyer Sharing Libs Custom Element 1 Custom Element 2 Custom
Element 3 Libraries: Angular, Bootstrap, … UMD Drawbacks: Complexity, no isolation

@ManfredSteyer 4) Choosing a Solution

@ManfredSteyer Some General Advice Shared state, navigation b/w apps Hyperlinks
Legacy Apps or *very very* strong isolation? iframes Separate Deployment/ mix Technologies? Bootstrap several SPAs Monorepo little much yes no yes no Not a good fit for public web sites Wrap as Web Component?

@ManfredSteyer Blog > SOFTWAREarchitect.io • A Software Architect's Approach Towards
Using Angular (And SPAs In General) For Microservices Aka Microfrontends • Micro Apps With Web Components Using Angular Elements • Angular Elements: A dynamic Dashboard … • Angular, React, Vue.Js And Co. Peacefully United Thanks To Micro Apps And Web Components

@ManfredSteyer Conclusion Micro App: Decoupling b/w Teams & Projects Best
Technology for your current project Web Components + Micro App = ❤️ You need to evaluate!

@ManfredSteyer Contact and Downloads [mail] [email protected] [web] SOFTWAREarchitect.io [twitter] ManfredSteyer
d Slides & Examples

Sustainable Client Architectures with Micro Apps

Sustainable Client Architectures with Micro Apps

More Decks by Manfred Steyer

Other Decks in Programming

Featured

Transcript