You Might Not Need NgRx
summary
Concrete claims about when NgRx helps and when it hurts guide the decision The talk contrasts benefits — serializability, immutability, type safety and easier testing — with measurable costs like complexity and a high code cost and cites 7 million downloads as evidence of growth It names the Sherri principle (shared hydrated available retrieved impacted) to classify hard state problems, shows a real reuse case sharing UI between a tiny IoT device and a cloud app, and lists alternatives like Akita and NgXS and pragmatic patterns such as behavior subjects are totally fine
AI-written summary · about
chapters (50)
- 0:00Intro
- 0:27Who am I
- 1:26How does my application change
- 3:27Elegant Complexity
- 4:37Requirements
- 5:15Complaint about NgRx
- 6:40Serializability
- 7:10Type Safety
- 7:34Testing
- 7:51Explicit code
- 8:09abstractions
- 8:41code cost
- 9:08benefits
- 9:33hallways
- 9:50interaction beam
- 10:11responsibilities
- 10:51Where are the books
- 11:45Action Mapping
- 12:34Indirection
- 13:24Complex state problems
- 13:35Shared state
- 13:55Hydrated state
- 14:38Available state
- 15:04Retrieve state
- 15:24Impacted state
- 16:18Quality
- 16:58Functional Purity
- 17:41Pure function
- 17:57Bootstrapped flag
- 18:24Peer function
- 18:42Get menu
- 18:55Side effects
- 19:14Effects
- 19:44Components
- 20:35Functions and Components
- 21:33Advantages of NgRx
- 21:52Architecture
- 22:27Content Creators
- 22:53Parallelization
- 23:17Effects and Reducers
- 23:39Index
- 24:01Smart Lighting
- 24:14Power
- 24:37Cloud
- 24:59Indirect
- 25:17Recap
- 25:51I want to start learning
- 26:02Behavior subjects
- 26:22Advanced use cases
- 26:46Conclusion
