Structure for big Angular Applications Packages, Monorepos & Micro Apps

@ManfredSteyer Structure for big Angular Applications Packages, Monorepos & Micro
Apps Manfred Steyer SOFTWAREarchitekt.at ManfredSteyer

@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: everywhere http://softwarearchitekt.at/workshops

@ManfredSteyer Goal Get to know three concepts for structuring big
Angular based enterprise application

@ManfredSteyer Contents 1) npm Packages 2) Monorepos 3) Micro Apps
4) How to choose?

@ManfredSteyer 1) npm Packages

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

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

@ManfredSteyer Lots of DETAILS

@ManfredSteyer Angular CLI 6+ supports Packages

@ManfredSteyer Create Library 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

@ManfredSteyer Folder Structure

@ManfredSteyer DEMO

@ManfredSteyer Deployment

@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

@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 • Decoupling between lib
authors and app authors

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

@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?

@ManfredSteyer 2) Monorepos

@ManfredSteyer Workspace

@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 DEMO

@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 Disadvantages More Coordination Blocking Tasks Complex Overall System One
Architecture One Technology Stack Hard to change One size fits all?

@ManfredSteyer 3) Micro Apps

@ManfredSteyer Idea System

@ManfredSteyer Idea µService µService µService

@ManfredSteyer Idea µApp µApp µApp

@ManfredSteyer Folie▪ 43 Pro Contra

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

@ManfredSteyer

@ManfredSteyer µService Providing a (SPA based) Shell µApp µApp µApp
Shell ✓ iframes ✓ Web Components ✓ Bootstrapping several SPAs

@ManfredSteyer Angular Elements

@ManfredSteyer MicroApp with Angular Elements @NgModule({ imports: [BrowserModule], declarations: [MicroAppComponent],
bootstrap: [], entryComponents: [MicroAppComponent] }) export class AppModule { }

bootstrap: [], entryComponents: [MicroAppComponent] }) export class AppModule { constructor(private injector: Injector) { } ngDoBootstrap() { } }

bootstrap: [], entryComponents: [MicroAppComponent] }) export class AppModule { constructor(private injector: Injector) { } ngDoBootstrap() { const MicroAppElement = createCustomElement( MicroAppComponent, { injector: this.injector }); customElements.define('micro-app', MicroAppElement); } }

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

@ManfredSteyer DEMO

@ManfredSteyer 4) Choosing a Solution

@ManfredSteyer Some General Advice for Macro-Architecture Shared state, navigation b/w
apps Hyperlinks Legacy Apps or *very very* strong isolation? iframes Separate Deployment/ mix Technologies? Web Components Monolith w/ Libs and Monorepo little much yes no yes no Not a good fit for public web sites

@ManfredSteyer Micro-Architecture Packages Web Components Monorepo Inner Sourcing …

@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 Conclusion Packages: Reuse Monorepo: Structure Microservices: Decoupling CLI 6+
CLI 6+/ Nx Links, iframes, Web Comp.

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

Structure for big Angular Applications Packages...

Structure for big Angular Applications Packages, Monorepos & Micro Apps

More Decks by Manfred Steyer

Featured

Transcript