Architectures for huge Enterprise Applications with Angular -- Slides from We Are Developers in Vienna, May 2018

Slide 1

Slide 1 text

@BASTAcon & @ManfredSteyer Architectures for huge Enterprise Applications with Angular Manfred Steyer SOFTWAREarchitekt.at ManfredSteyer

Slide 2

Slide 2 text

@BASTAcon & @ManfredSteyer About me… • Manfred Steyer • SOFTWAREarchitekt.at • Angular Trainings and Consultancy • Google Developer Expert (GDE) Page ▪ 4 Manfred Steyer Vienna: June 2018 In-House: Every time

Slide 3

Slide 3 text

@ManfredSteyer Typical Module Structure Page ▪ 5 AppModule … … … SharedModule Root Module Feature Modules Shared Module

Slide 4

Slide 4 text

@ManfredSteyer Contents • (npm-)Packages • Monorepos • Microservices

Slide 5

Slide 5 text

@ManfredSteyer npm Packages

Slide 6

Slide 6 text

@ManfredSteyer Structure of an npm Package • /node_modules • your-stuff • package.json

Slide 7

Slide 7 text

@ManfredSteyer Angular Package Format https://goo.gl/hjt7G3

Slide 8

Slide 8 text

@ManfredSteyer Lots of DETAILS

Slide 9

Slide 9 text

@ManfredSteyer ng-packagr

Slide 10

Slide 10 text

@ManfredSteyer Angular CLI 6+ supports Packages using ng-packagr

Slide 11

Slide 11 text

@ManfredSteyer Create Library with CLI >= 6 npm install -g @angular/cli ng new lib-project cd lib-project ng generate library logger-lib ng generate application playground-app ng serve --project playground-app ng build --project logger-lib

Slide 12

Slide 12 text

@ManfredSteyer Folder Structure

Slide 13

Slide 13 text

@ManfredSteyer Deployment

Slide 14

Slide 14 text

@ManfredSteyer Publishing to npm Registry • Increment version in package.json • npm version [patch | minor | major | version] • ng build --project logger-lib • npm publish --registry http://localhost:4873 • npm install --registry http://localhost:4873

Slide 15

Slide 15 text

@ManfredSteyer Alternatives for setting the Registry • Global: npm set registry http://localhost:4873 • Default: registry.npmjs.org • npm get registry • Project: .npmrc in project root

Slide 16

Slide 16 text

@ManfredSteyer npm Registries Nexus Artifactory Team Foundation Server Verdaccio npm i -g verdaccio verdaccio

Slide 17

Slide 17 text

@ManfredSteyer Advantages • Distribution • Versioning • Decoupling between lib authors and app authors

Slide 18

Slide 18 text

@ManfredSteyer Disadvantages • Distribution • Versioning • Decoupling between lib authors and app authors ;-)

Slide 19

Slide 19 text

@ManfredSteyer Disadvantages Distribution • Annoying within project • Prevents gritting further libs Versioning • Old versions • Conflicts • How to force devs to use latest version? Decoupling • What if lib authors == app authors?

Slide 20

Slide 20 text

@ManfredSteyer Monorepos

Slide 21

Slide 21 text

@ManfredSteyer Monorepo Structure

Slide 22

Slide 22 text

@ManfredSteyer Advantages Everyone uses the latest versions No version conflicts No burden with distributing libs Creating new libs: Adding folder Experience: Successfully used at Google, Facebook, …

Slide 23

Slide 23 text

@ManfredSteyer Two Flavors • Like Workspaces/Solutions in different IDEs Project Monorepo • E. g. used at Google or Facebook Company-wide Monorepo

Slide 24

Slide 24 text

@ManfredSteyer Moving back and forth

Slide 25

Slide 25 text

@ManfredSteyer Moving back and forth Npm Registry

Slide 26

Slide 26 text

@ManfredSteyer Alternative Git Repo Git-based Sub-Module (read only or read/write)

Slide 27

Slide 27 text

@ManfredSteyer Tooling & Generator https://nrwl.io/nx

Slide 28

Slide 28 text

@ManfredSteyer Further Features of Nx • Just recompile changed apps • Format Code/ check format • Restrict which apps/libs can access which other libs • Visualize module structure and dependencies • Scaffold Boilerplate

Slide 29

Slide 29 text

@ManfredSteyer DEMO

Slide 30

Slide 30 text

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

Slide 31

Slide 31 text

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

Slide 32

Slide 32 text

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

Slide 33

Slide 33 text

@ManfredSteyer Disadvantages More Coordination Blocking Tasks Complex Overall System One Architecture One Technology Stack Hard to change One size fits all?

Slide 34

Slide 34 text

@ManfredSteyer Microservices

Slide 35

Slide 35 text

@ManfredSteyer Idea System

Slide 36

Slide 36 text

@ManfredSteyer Idea µService µService µService

Slide 37

Slide 37 text

@ManfredSteyer Idea µApp µApp µApp

Slide 38

Slide 38 text

@ManfredSteyer Folie▪ 47 Pro Contra

Slide 39

Slide 39 text

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

Slide 40

Slide 40 text

@ManfredSteyer

Slide 41

Slide 41 text

@ManfredSteyer

Slide 42

Slide 42 text

@ManfredSteyer

Slide 43

Slide 43 text

@ManfredSteyer µService Providing a (SPA based) Shell µApp µApp µApp Shell

Slide 44

Slide 44 text

@ManfredSteyer Some Options for Shell iframes • Strong Isolation • Straight forward • Overlapping Elements? • Lots of page requests? • SEO? Web Components • Standard • Custom Elements • • • Shadow DOM: CSS Isolation • Nesting • Framework Support? Bootstrapping different SPAs • Similar to Web Components • No Standard • Nesting isn’t possible

Slide 45

Slide 45 text

@ManfredSteyer Angular Elements in Angular >= 6

Slide 46

Slide 46 text

Slide 47

Slide 47 text

Slide 48

Slide 48 text

Slide 49

Slide 49 text

@ManfredSteyer MicroApp with Angular Elements @NgModule({ imports: [BrowserModule], declarations: [MicroAppComponent], bootstrap: [], entryComponents: [MicroAppComponent] }) export class AppModule { constructor(private injector: Injector) { } ngDoBootstrap() { const MicroAppElement = createNgElementConstructor( MicroAppComponent, { injector: this.injector }); customElements.define('micro-app', MicroAppElement); } }

Slide 50

Slide 50 text

@ManfredSteyer Loading MicroApps

Slide 51

Slide 51 text

@ManfredSteyer DEMO

Slide 52

Slide 52 text

@ManfredSteyer Some General Advice for Macro-Architecture Shared state, communication/ navigation b/w apps Hyperlinks Legacy Apps or *very very* strong isolation needed? iframes Need separate Deployment/ mix Technologies Web Components "Majestic Monolith" w/ Libs and Monorepo little much yes no yes no Not a good fit for customer facing Fallback: Bootstrap several frameworks/ Spa Micro-Architecture: • Libs/ npm packages • Monorepo • Web Components • …

Slide 53

Slide 53 text

@ManfredSteyer Blog • 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 • Microservice Clients With Web Components Using Angular Elements: Dreams Of The (Near) Future?

Slide 54

Slide 54 text

@ManfredSteyer Conclusion Packages: Reuse Monorepo: Structure Microservices: Decoupling CLI 6+ CLI 6+/ Nx Links, iframes, Web Comp.

Slide 55

Slide 55 text

@ManfredSteyer Contact and Downloads [mail] manfred.steyer@SOFTWAREarchitekt.at [web] SOFTWAREarchitekt.at [twitter] ManfredSteyer d