Optimizing Data Handling
summary
Describes a concrete migration from RxJS-based BehaviorSubject stores to Angular 16 signals with real code: a reusable custom CacheOperator that loads, caches and invalidates data; a sandbox/store pattern that reduces duplicate API calls and isolates UI from business logic; measured wins are fewer redundant requests and faster UI rendering; invalidation strategies include router-driven feature-based storage clearing and push updates via server-sent events with SignalR while keeping interoperability with observables.
AI-written summary · about
chapters (15)
- 0:00Data handling optimization
- 1:10Local cache vs API requests
- 2:36Storage and sandbox services
- 4:28Reactive data flows with RXJS
- 9:54Angular signals for performance
- 13:26Cache operator for API interoperability
- 17:52Cache operator for Angular signals
- 19:43Data invalidation strategies
- 20:48Event-based invalidation
- 22:17Real-time updates with SSE
- 24:27Architecture impacts
- 24:48Angular updates and signals
- 25:55Cache operator future
- 27:27Complex data storage utilities
- 33:47Summary and Q&A
related talks
18mNgRx SignalStore: Modern State Management for Angular
36mEffective Signals in Angular 19 and above: Rules and Helpers
14mAngular w Signals
41mAngular Signals: What's All the Fuss About?
31mNgRx SignalStore: The Ultimate Tool for Modern State Management
20mSubjecting State to Good Behavior
30mSignals Unleashed: Intro to NgRx Signal Store
34mReactive State Management For Your Angular App