Angular Architecture using Signals
summary
Claims that Angular Signals replace observables for many app needs and make change detection selective and cheaper. Walkthroughs show writable/computed/effect primitives, a linked signal used to reset a select index, and a resource loader that returns a Promise and exposes status loading→resolved/error plus request/refresh/abort behavior. Examples compare RxJS vs resource, note resources can be moved into services or injectables, and showcase an app rebuild with SSR and signals; NGX ships a signal store and forms move toward signal-based APIs.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:09Angular Love blog projects
- 2:11What are signals
- 4:16Effects and proper use
- 5:39Linked signals for sync
- 7:50Signals and change detection
- 9:39Simpler components with signals
- 11:27New lifecycle hooks
- 12:29State management evolution
- 16:40Managing resources
- 18:06Signal Store in NGX Store
- 19:55Future forms with signals
- 21:00Summary and future
- 21:25Q&A
related talks
32mEverything you need to know about Angular Signals
51mSignals in Angular: How Do They Work?
36mEffective Signals in Angular 19 and above: Rules and Helpers
19mAngular Signals: A Look Under the Hood and Beyond
41mAngular Signals: What's All the Fuss About?
20mAngular Signals under the Hood
14mAngular w Signals
31mSignals & fine grained reactivity in Angular