Architectures for big Enterprise Applications with Angular -- Talk from Frontend Usergroup RheinMain, June 2018

# Library DEMO - npm package with CLI 6
https://github.com/manfredsteyer/cli6-based-lib-demo

# Monorepo DEMO with Nx
https://github.com/manfredsteyer/monorepo-demo

# Micro Apps with Angular Elements DEMO
https://github.com/manfredsteyer/angular-microapp
Have a look at the README.md

# Blog Post about Micro Apps with Angular Elements
http://www.softwarearchitekt.at/post/2018/05/04/microservice-clients-with-web-components-using-angular-elements-dreams-of-the-near-future.aspx

# More Information & Workshops
http://www.softwarearchitekt.at/

Transcript

1. @ManfredSteyer Architectures for huge Enterprise Applications with Angular Manfred Steyer SOFTWAREarchitekt.at ManfredSteyer
2. @ManfredSteyer About me… • Manfred Steyer • SOFTWAREarchitekt.at • Angular Trainings and Consultancy • Google Developer Expert (GDE) Page ▪ 3 Manfred Steyer Public: Vienna, München, Zürich In-House: Every where, every time http://softwarearchitekt.at/workshops
3. @ManfredSteyer Goal Get to know three concepts for structuring big Angular based enterprise application
4. @ManfredSteyer Contents 1) npm Packages 2) Monorepos 3) Micro Apps 4) How to choose?
5. @ManfredSteyer 1) npm Packages
6. @ManfredSteyer Structure of an npm Package • /node_modules • your-stuff • package.json
7. @ManfredSteyer Angular Package Format https://goo.gl/hjt7G3
8. @ManfredSteyer Lots of DETAILS
9. @ManfredSteyer Angular CLI 6+ supports Packages
10. @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
11. @ManfredSteyer Folder Structure
12. @ManfredSteyer DEMO
13. @ManfredSteyer Deployment
14. @ManfredSteyer Publishing to npm Registry • Increment version in package.json • ng build --project logger-lib • npm publish --registry http://localhost:4873 • npm install --registry http://localhost:4873
15. @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
16. @ManfredSteyer npm Registries Nexus Artifactory Team Foundation Server Verdaccio npm i -g verdaccio verdaccio
17. @ManfredSteyer DEMO
18. @ManfredSteyer Advantages • Distribution • Versioning • Decoupling between lib authors and app authors
19. @ManfredSteyer Disadvantages • Distribution • Versioning • Decoupling between lib authors and app authors ;-)
20. @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?
21. @ManfredSteyer 2) Monorepos
22. @ManfredSteyer Workspace
23. @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, …
24. @ManfredSteyer Two Flavors • Like Workspaces/Solutions in different IDEs Project Monorepo • E. g. used at Google or Facebook Company-wide Monorepo
25. @ManfredSteyer Moving back and forth Npm Registry
26. @ManfredSteyer Moving back and forth Git Repo Git-based Sub-Module (read only or read/write)
27. @ManfredSteyer Tooling & Generator https://nrwl.io/nx
28. @ManfredSteyer Visualize Module Structure
29. @ManfredSteyer DEMO
30. @ManfredSteyer Advantages Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project
31. @ManfredSteyer Disadvantages Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project
32. @ManfredSteyer Disadvantages Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Team A Team B Contract
33. @ManfredSteyer Disadvantages More Coordination Blocking Tasks Complex Overall System One Architecture One Technology Stack Hard to change One size fits all?
34. @ManfredSteyer 3) Micro Apps
35. @ManfredSteyer Idea System
36. @ManfredSteyer Idea µService µService µService
37. @ManfredSteyer Idea µApp µApp µApp
38. @ManfredSteyer Folie▪ 43 Pro Contra
39. @ManfredSteyer UI Composition w/ Hyperlinks µApp SPA µApp SPA µApp SPA
40. @ManfredSteyer
41. @ManfredSteyer
42. @ManfredSteyer
43. @ManfredSteyer µService Providing a (SPA based) Shell µApp µApp µApp Shell
44. @ManfredSteyer µService iframes iframe iframe iframe Shell ✓ Strong Isolation ✓ Straight forward  Overlapping Elements?  Lots of page requests?  SEO?  Resize iframe
45. @ManfredSteyer µService Web Components Web Component Web Component Web Component Shell  Standard  Frameworkunabhängig  Custom Elements  <app-a></app-a>  <app-b></app-b>  Shadow DOM: CSS Isolation  Nesting  Framework Support?
46. @ManfredSteyer µService Mehrere SPAs in index.html SPA SPA SPA Shell ✓ Similar to Web Components  No Standard  Nesting isn’t possible
47. @ManfredSteyer Angular Elements in Angular >= 6
48. @ManfredSteyer MicroApp with Angular Elements @NgModule({ imports: [BrowserModule], declarations: [MicroAppComponent], bootstrap: [], entryComponents: [MicroAppComponent] }) export class AppModule { }
49. @ManfredSteyer MicroApp with Angular Elements @NgModule({ imports: [BrowserModule], declarations: [MicroAppComponent], bootstrap: [], entryComponents: [MicroAppComponent] }) export class AppModule { }
50. @ManfredSteyer MicroApp with Angular Elements @NgModule({ imports: [BrowserModule], declarations: [MicroAppComponent], bootstrap: [], entryComponents: [MicroAppComponent] }) export class AppModule { constructor(private injector: Injector) { } ngDoBootstrap() { } }
51. @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); } }
52. @ManfredSteyer Loading MicroApps <script src="micro-app.bundle.js"></script> <micro-app></micro-app>
53. @ManfredSteyer DEMO
54. @ManfredSteyer 4) Choosing a Solution
55. @ManfredSteyer Some General Advice for Macro-Architecture Shared state, 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 when customer facing
56. @ManfredSteyer Conclusion Packages: Reuse Monorepo: Structure Microservices: Decoupling CLI 6+ CLI 6+/ Nx Links, iframes, Web Comp.
57. @ManfredSteyer Contact and Downloads [mail] manfred.steyer@SOFTWAREarchitekt.at [web] SOFTWAREarchitekt.at [twitter] ManfredSteyer d http://softwarearchitekt.at/workshops Slides & Examples