Sustainable Client Architectures with Angular and Micro Apps @BASTA 2016 in Mainz, Germany

@ManfredSteyer Sustainable Client Architectures with Angular and Micro Apps Manfred
Steyer SOFTWAREarchitekt.at ManfredSteyer

@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
- 20 yrs

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

@ManfredSteyer Idea System

@ManfredSteyer Idea µService µService µService

@ManfredSteyer Idea µService µService µService Single Page Application ??

@ManfredSteyer Contents 1) Deployment Monolith 2) Hyperlinks 3) Shell 4)
How to choose?

@ManfredSteyer About me… • Manfred Steyer SOFTWAREarchitekt.at • Angular Trainings
and Consultancy • Google Developer Expert (GDE) • Collaborator in the Angular Team Page ▪ 12 Manfred Steyer Public: Frankfurt, Munich, Vienna In-House: everywhere http://softwarearchitekt.at/workshops

@ManfredSteyer 1) Deployment Monolith

@ManfredSteyer Idea µService µService µService Client Fragment Client Fragment Client
Fragment ✓ Easy (Tooling) ✓ One optimized Bundle ✓ Consistent  No separate deployment  Mixing Technologies: Difficult npm Packages ?

@ManfredSteyer Advantages • Distribution • Versioning

@ManfredSteyer Disadvantages • Distribution • Versioning ;-)

@ManfredSteyer Disadvantages Distribution • Annoying within project Versioning • Old
versions • Conflicts • How to force devs to use latest version?

@ManfredSteyer Monorepo

@ManfredSteyer Workspace

@ManfredSteyer Advantages Sub Project Sub Project Sub Project Sub Project
Sub Project Sub Project Sub Project Sub Project

@ManfredSteyer Disadvantages Sub Project Sub Project Sub Project Sub Project
Sub Project Sub Project Sub Project Sub Project

@ManfredSteyer Disadvantages Sub Project Sub Project Sub Project Sub Project
Sub Project Sub Project Sub Project Sub Project Team A Team B Contract

@ManfredSteyer Solution Sub Project Sub Project Sub Project Sub Project
Sub Project Sub Project Sub Project Sub Project Team A Team B

@ManfredSteyer Solution App App App App Lib Lib Lib Lib
Team A Team B Lib Lib Shared Libs Lib

@ManfredSteyer One or many repos? • Full isolation • Different
lib versions • Difficult to shared code (npm) Multiple Repos • Less isolation, however: Nx allows to restrict access b/w libs • Often: One-Version-Policy (depends on implementation) • Easy to shared code Monorepo More "by the book" Pragmatic Solution

@ManfredSteyer Solution App App App App Lib Lib Lib Lib
How to "integrate" apps for the user?

@ManfredSteyer 2) Hyperlinks

@ManfredSteyer UI Composition w/ Hyperlinks µApp SPA µApp SPA µApp
SPA

@ManfredSteyer

@ManfredSteyer ✓ Simple  Loosing State  Load a new
Application

@ManfredSteyer

@ManfredSteyer Web Components for Shared Widgets?

@ManfredSteyer 3) Shell

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

@ManfredSteyer Loading MicroApps <script src="micro-app.bundle.js"></script> <micro-app></micro-app>

@ManfredSteyer DEMO

@ManfredSteyer Lazy Loading const script = document.createElement('script'); script.src = 'assets/external-dashboard-tile.bundle.js';
document.body.appendChild(script); const clientA = document.createElement('client-a'); clientA['visible'] = true; document.body.appendChild(clientA);

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

@ManfredSteyer Communication client-a/this/that?customerId=17 client-b/this/that?customerId=17 client-c/this/that?customerId=17

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

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

@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 Monolith w/ Libs and Monorepo little much yes no yes no Not a good fit for public web sites

@ManfredSteyer Architecture within Micro-Apps Packages Web Components Monorepo Inner Sourcing
Separate Wey …

@ManfredSteyer Blog > SOFTWAREarchitekt.at • A Software Architect's Approach Towards
Using Angular (And SPAs In General) For Microservices Aka Microfrontends • A Lightweight And Solid Approach Towards Micro Frontends (Micro Service Clients) With Angular And/Or Other Frameworks • Micro Apps With Web Components Using Angular Elements

@ManfredSteyer Contact and Downloads [mail] [email protected] [web] SOFTWAREarchitekt.at [twitter] ManfredSteyer
d Slides & Examples http://softwarearchitekt.at/workshops

Sustainable Client Architectures with Angular and Micro Apps @BASTA 2016 in Mainz, Germany

Sustainable Client Architectures with Angular and Micro Apps @BASTA 2016 in Mainz, Germany

More Decks by Manfred Steyer

Other Decks in Programming

Featured

Transcript