3. ME
• Angular(JS) user since 2013
• own a small consultant company Zalari GmbH in Dresden
• use of Angular at various DAX companies
• founder of JavaScript MeetUp in Dresden 2015
• have strong opinions and loves to constructively argue
about them -> @WalterFaber onTwitter
13. MONOLITHS LOOK COOL,
BUTTHAT’S IT
• We happily used Angular to build „modular“ frontend monoliths, that
suck have some issues:
• no easy out of the box runtime composition
• vendor lock-in to the one platform (to rule them all)
• https://github.com/angular/angular/issues/18155
• …
• no easy reuse of (UI) components in other technology stacks
14. ANGULAR UI COMPONENTS
ARE DEAD
• Angular UI components on their own cannot be easily reused
• Guess what: Google is building Material WebComponents,
that are re-usable
• … and they are not using Angular…
• there are other companies taking a similar approach
• OnsenUI…
17. –ThoughtWorksTechnology Radar
„A web application is broken up by its pages and
features, with each feature being owned end-to-
end by a single team. […], but the goal remains to
allow each feature to be developed, tested and
deployed independently from others.
https://www.thoughtworks.com/de/radar/techniques/micro-frontends
18. MICRO FRONTENDS
• they solve all your problems™ , just as micro
services do!
• Angular is not well-suited for Micro Frontends
• …that are technology agnostic
21. ANGULAR IS NOT DEADYET
• it depends: if you building your micro frontend
architecture on top of WebComponents
• there is Angular Elements
• Angular can still be a nice host for your micro
frontend platform
22. RECAP
• Deal with Micro Frontends they are cool!
• Angular Elements allows for true WebComponents that allow for
true reuse in other stacks that are perfect building blocks for a
technology agnostic Micro Frontend architecture
• but so does StencilJS, that uses a lot of Angular’s component ideas…
• shameless plug:
• https://github.com/ChristianUlbrich/awesome-microfrontends