Architectures for you big Angular applications: npm-Packages, Monorepos, and Microfrontends @DevWeek 2019 in Nuremberg

Transcript

1. @ManfredSteyer Architectures for you big Angular applications: npm-Packages, Monorepos, and Microfrontends Manfred Steyer SOFTWAREarchitekt.at ManfredSteyer
2. @ManfredSteyer Ever started a project from the scratch? Kick-off After some weeks After some years
3. @ManfredSteyer Contents 1) npm Packages 2) Monorepos 3) Micro Apps 4) Choosing a solution
4. @ManfredSteyer About me… • Manfred Steyer SOFTWAREarchitekt.at • Angular Trainings and Consultancy • Google Developer Expert (GDE) • Trusted Collaborator for Angular Team Page ▪ 4 Manfred Steyer In-House: everywhere! Public: Wien - München - Frankfurt http://softwarearchitekt.at/workshops
5. @ManfredSteyer 1) npm Packages
6. @ManfredSteyer Why Packages? Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project
7. @ManfredSteyer Create Packages with CLI >= 6 npm install -g @angular/cli ng new lib-project cd lib-project ng generate library flight-booking-lib ng generate application playground-app ng serve --project playground-app ng build --project flight-booking-lib
8. @ManfredSteyer Folder Structure
9. @ManfredSteyer Publishing to npm Registry • Increment version in package.json • ng build --project flight-booking-lib • npm publish --registry http://localhost:4873 • npm install --registry http://localhost:4873
10. @ManfredSteyer Alternatives for setting the Registry • Global: npm set registry http://localhost:4873 • Project: .npmrc in project root
11. @ManfredSteyer npm Registries Nexus Artifactory Team Foundation Server Verdaccio npm i -g verdaccio verdaccio
12. @ManfredSteyer Advantages • Distribution • Versioning
13. @ManfredSteyer Disadvantages • Distribution • Versioning ;-)
14. @ManfredSteyer Disadvantages Distribution • Annoying within project • Prevents gritting further libs Versioning • Old versions • Conflicts • How to force devs to use latest version?
15. @ManfredSteyer 2) Monorepos
16. @ManfredSteyer Workspace
17. @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, …
18. @ManfredSteyer Moving back and forth Npm Registry
19. @ManfredSteyer DEMO
20. @ManfredSteyer Tooling & Generator https://nrwl.io/nx
21. @ManfredSteyer Visualize Module Structure
22. @ManfredSteyer Booking Boarding Shared Feature Feature Feature Feature Feature UI UI UI UI UI UI UI UI UI Domain Domain Domain Domain Domain Domain Util Util Util Util Util Util Enterprise Monorepo Patterns, Nrwl 2018: https://tinyurl.com/y2jjxld7 @ManfredSteyer Shared Kernel (if really needed) & other libs
23. @ManfredSteyer Booking Boarding Shared Feature API Feature Feature Feature Feature UI UI UI UI UI UI UI UI UI Domain Domain Domain Domain Domain Domain Util Util Util Util Util Util @ManfredSteyer
24. @ManfredSteyer Finegrained Libraries • Unit of recompilation • Unit of retesting • Access restrictions • Prevent Cycles • Information Hiding • Future replacement for NgModules?
25. @ManfredSteyer DEMO
26. @ManfredSteyer Advantages Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project
27. @ManfredSteyer Disadvantages Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project
28. @ManfredSteyer Disadvantages Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Sub Project Team A Team B Contract Maintainability? One Architecture/ One Framework
29. @ManfredSteyer 3) Micro Apps
30. @ManfredSteyer Idea µService µService µService
31. @ManfredSteyer Idea µApp µApp µApp
32. @ManfredSteyer Booking Boarding Shared Feature Feature Feature Feature Feature … … … … … … … … … @ManfredSteyer Booking App Boarding App Option 1: One App per Domain
33. @ManfredSteyer Booking Boarding Shared Feature Feature Feature Feature Feature … … … … … … … … … @ManfredSteyer Booking App Boarding App Option 2: One Monorepo per Domain Publish shared libs seperately via npm
34. @ManfredSteyer Folie▪ 43 Pro Contra
35. @ManfredSteyer UI Composition w/ Hyperlinks µApp SPA µApp SPA µApp SPA <a href="…>…</a> <a href="…>…</a>
36. @ManfredSteyer
37. @ManfredSteyer
38. @ManfredSteyer ✓ Simple  Loosing State  Load a new Application  Consistent Look and Feel
39. @ManfredSteyer
40. @ManfredSteyer Web Components for Shared Widgets? Mehr dazu: 18:15, Honkong: Angular Elements & Ivy
41. @ManfredSteyer µService Providing a (SPA based) Shell µApp µApp µApp Shell ▪ iframes ▪ Bootstrapping several SPAs ▪ Consider Lazy Loading!
42. @ManfredSteyer 3) DEMO
43. @ManfredSteyer Advantages • Several small and decoupled Projects • Autarkic Teams • Seperate development/ deployment • Own decisions (technology, architecture)
44. @ManfredSteyer Disadvantages ;-) • Several small and decoupled Projects • Autarkic Teams • Seperate development/ deployment • Own decisions (technology, architecture)
45. @ManfredSteyer Disadvantages ;-) • More Bundles • Less optimized Bundles/ duplicate Code? • UI Consistency
46. @ManfredSteyer 4) Choosing a Solution
47. @ManfredSteyer Macro Architecture 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
48. @ManfredSteyer Micro Architecture Npm Packages Web Components Inner Sourcing Seperate Ways …
49. @ManfredSteyer Blog > SOFTWAREarchitekt.at • Sustainable Angular Architectures With Strategic Design And Monorepos • 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
50. @ManfredSteyer Conclusion Packages: Reuse Monorepo: Structure Micro Apps: Decoupling CLI 6+ CLI 6+/ Nx Links, iframes, n SPAs, Web Components
51. @ManfredSteyer Beware the Frankenstein- Monster!!
52. @ManfredSteyer Contact and Downloads [mail] manfred.steyer@SOFTWAREarchitekt.at [web] SOFTWAREarchitekt.at [twitter] ManfredSteyer d http://softwarearchitekt.at/workshops In-House: Everywhere Public: Wien - München - Frankfurt Slides & Examples