Hackathon_2018.pdf

Transcript

1. Hackathon 2018 Modular Angular Framework
2. • Navigating between apps is slow • Updating component libraries (eg. navbar) requires “bumping” Problems
3. Solution • Serve 1 Angular application • Use Lazy Loading feature to load “apps” (eg. Central, LH) • Use similar technique to load navbar, no bumping required
4. Overview Core (PCF App) Navbar Central LH User Static Bundle Server (PCF App) Lazy load request deploys Separate repo, build, version, etc Bundles (app, component modules, etc
5. How does a bundle get updated? (eg. navbar) 1. Make changes to navbar, open PR, merge PR 2. Build system creates a special lazy-loadable bundle 3. Bundle gets uploaded to the static bundle server app 4. Refresh your browser 5. New version of navbar is installed!
6. Pros and Cons • Faster initial page load ◦ Small core ◦ Ahead-of-Time compiled • No more loading when switching apps • No more “bumping” ◦ Faster dev cycle • Tighter dependency management ◦ ie all app have same version of angular • All apps always have latest version navbar • Apps can still use their own 3rd party packages for stuff (eg. charts) • Tighter dependency management ◦ Mitigation: Take your app bundle and serve it stand alone like we normally do
7. Demo • http://picarm1-hackathon-bundles.apps.titan.lab.emc.com/ • http://picarm1-hackathon-core.apps.titan.lab.emc.com/ repos: https://gssd-stash.isus.emc.com/users/picarm1 (all named hackathon-*)