State Management — One Meta-Model to Rule Them All
summary
Shows how a small set of architecture principles—a single store as the single source of truth, pure reducer functions that return new state, and explicit handling of side effects—lets different state-management libraries be compared and interchanged. Compares ngRx, MobX and redux-observable by concrete design choices, demonstrates push-based architectures and selector patterns, and explains when a simple service can be preferable to a full library (including support for optimistic updates and time-travel debugging).
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:17Single source of truth
- 5:22State consistency
- 7:23Pure functions
- 10:08Push-based benefits
- 12:35State architecture
- 16:10Seven principles
- 18:16Q&A
related talks
27mCrafting state management – A principle based architecture
41mThe Battle of State Management in modern frontend applications
52mState management beyond the libraries
39mState Management with Redux
41mManaging State in Angular Applications
14mState management without pain
30mMake React State-Management great again
52mState Management in Angular: From Facades to NgRx and back