Structure For Your Huge Angular Solutions: Packages, Monorepos and Micro Frontends @AngularDays

@BASTAcon & @ManfredSteyer Structure For Your Huge Angular Solutions: Packages,
Monorepos and Micro Frontends

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

@ManfredSteyer Contents • (npm-)Packages • Nx Monorepos • Strategic Design
and DDD • Microfrontends

@ManfredSteyer Manfred Steyer

@ManfredSteyer npm Packages

@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

@ManfredSteyer Folder Structure

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

@ManfredSteyer Publishing

@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

@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

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

@ManfredSteyer DEMO

@ManfredSteyer Advantages • Distribution • Versioning

@ManfredSteyer Disadvantages • Distribution • Versioning ;-)

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

@ManfredSteyer Monorepos

@ManfredSteyer Monorepo Structure

@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, …

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

@ManfredSteyer Moving back and forth Npm Registry

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

@ManfredSteyer Visualize Module Structure

@ManfredSteyer Creating a Workspace npm install -g @angular/cli ng new
workspace cd workspace ng generate app my-app ng generate lib my-lib ng serve --project my-app ng build --project my-app

@ManfredSteyer Creating a Workspace npm install -g @angular/cli npm init
nx-workspace myworkspace cd workspace ng generate app my-app ng generate lib my-lib ng serve --project my-app ng build --project my-app

@ManfredSteyer DEMO

@ManfredSteyer LAB

@ManfredSteyer DDD in a nutshell

@ManfredSteyer Methodology for bridging the gap b/w requirements and architecture/
design

@ManfredSteyer

@ManfredSteyer Domain Driven Design Strategic Design Tactical Design Decomposing a
System Design Patterns & Practices

@ManfredSteyer

@ManfredSteyer Example Flight System

@ManfredSteyer Booking Check-in Boarding Luggage Example Sub-Domains

@ManfredSteyer Booking Luggage Boarding Check-in Context Map

@ManfredSteyer Luggage Booking Context Map Check-in Boarding Shared Kernel

@ManfredSteyer Booking Check-in API

@ManfredSteyer Lots of approaches for cross-domain communication and more …

@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 Smart Comp. Dumb Comp.

@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

@ManfredSteyer Application Domain Model Infrastructure Isolate your domain! Domain e.
g. data access Use case specific facades, state management Entities, biz logic

@ManfredSteyer Alternatives to layering • e. g. Hexagonal Architecture, Clean
Architecture • Anyway: We need to restrict access b/w libraries

@ManfredSteyer DEMO

@ManfredSteyer Finegrained Libraries • Unit of recompilation • Unit of
retesting • Access restrictions • Information Hiding • Easy: Just ng g lib … • Future replacement for NgModules?

@ManfredSteyer Micro Frontends? Short outlook

@ManfredSteyer Booking App Check-in App Boarding App Luggage App Microfrontends

@ManfredSteyer

@ManfredSteyer Booking Boarding Shared Feature Feature Feature Feature Feature …
… … … … … … … … @ManfredSteyer Flight App Deployment Monolith

… … … … … … … … Booking App Boarding App Microfrontends

… … … … … … … … Booking App Boarding App Option 1: One App per Domain Monorepo

… … … … … … … … Booking App Boarding App Option 2: One Monorepo per Domain Publish shared libs seperately via npm Repository n Repository 2 Repository 1

@ManfredSteyer Benefits Autonomous Teams Separate Development Separate Deployment Own architecture
decisions Own technology descisions

@ManfredSteyer Integration via Hyperlinks

@ManfredSteyer

@ManfredSteyer Integration via Shell

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

@ManfredSteyer Loading Separately Compiled SPAs const script = document.createElement('script'); script.src
= 'assets/micro-app.bundle.js'; document.body.appendChild(script); const clientA = document.createElement('client-a'); clientA['visible'] = true; document.body.appendChild(clientA);

@ManfredSteyer

@ManfredSteyer Idea const Component = import('http://other-app/xyz') Does not work with
webpack/ Angular CLI Even lazy parts must be known at compile time!

@ManfredSteyer Webpack 5 Module Federation Shell (Host) Microfrontend (Remote) //
Maps Urls in // webpack config remotes: { mfe1: "mfe1" } // Expose files in // webpack config exposes: { Cmp: './my.cmp.ts' } import('mfe1/Cmp')

@ManfredSteyer How to Get the Microfrontend's URL? Shell (Host) Microfrontend
(Remote) RemoteEntrypoint.js <script src="…"></script>

@ManfredSteyer How to Share Libs? Shell (Host) Microfrontend (Remote) shared:
[ "@angular/core", "…" ] shared: [ "@angular/core", "…" ]

@ManfredSteyer DEMO

@ManfredSteyer

@ManfredSteyer Well … Webpack 5 is currently beta Shown examples:
PoC w/ custom webpack conf + patched CLI lib CLI: Not before version 11 (fall 2020) Custom Builder (e. g. ngx-build-plus)

@ManfredSteyer Free eBook ANGULARarchitects.io/book Updated for Module Federation and Alternatives

@ManfredSteyer 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? Load Bundles on Demand Monolith little much yes no yes no Not a good fit for public web sites

Structure For Your Huge Angular Solutions: Packages, Monorepos and Micro Frontends @AngularDays

Structure For Your Huge Angular Solutions: Packages, Monorepos and Micro Frontends @AngularDays

More Decks by Manfred Steyer

Featured

Transcript

Structure For Your HugeAngular Solutions: Packages, Monorepos andMicro Frontends @AngularDays