How Signals shape a Pull-based architecture
summary
Claims that switching to Signals plus Angular Change Detection produces a pull-based architecture where reads are synchronous and writes schedule asynchronous updates. Shows concrete swaps: computed replaces combineLatest and the async/|ngIf| pipe for synchronous state derivation; introduces link signal introduced in v19 for writable inputs and a resource pattern (idle|loading|error) for async state. Framework coalesces dirtiness, schedules updates via timers/RAF, re-renders only dirty components, and avoids glitches and repeated recomputation.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:11Signals vs observables debate
- 2:35Talk overview
- 3:50Sync vs async signals
- 6:10Change detection in Angular
- 9:49Push-based challenges
- 11:38Signals in templates
- 13:25Reactive tree and glitches
- 16:11UI as state function
- 18:41Effects vs derivation
- 21:08Sync derivation with signals
- 23:23Async derivation with resources
- 24:49Reactivity tree in components
- 25:53Pull-based benefits
- 27:17Summary
related talks
19mAngular Signals: A Look Under the Hood and Beyond
41mAngular Signals: What's All the Fuss About?
24mAngular Architecture using Signals
48mJS Signals
32mEverything you need to know about Angular Signals
20mAngular Signals under the Hood
31mSignals & fine grained reactivity in Angular
27mA Deep Dive into Fine-Grained Reactivity and the future of Signals