The State of State
summary
Compares approaches to managing application state, naming and evaluating Services (traditional service-based design), CQS/CQRS, Redux (stateless unidirectional dataflow), MobX as an alternative to Redux, DCI (Data, Context, Interaction) from OOP, and an author’s custom technique called MALEVICH, discussing pros and cons of each.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:11About me and frontend architecture
- 3:16State problem in frontend
- 7:37Why not store state in components
- 10:46Angular service approach
- 14:00State duplication problem
- 17:19CQRS pattern
- 22:02Redux overview and principles
- 26:17Redux duplication solution
- 30:30MobX approach and features
- 35:50CQRS pattern explained
- 42:11Malewich architecture
- 49:18Approach comparison and recommendations
- 50:01Q&A
related talks
41mThe Battle of State Management in modern frontend applications
18mState Management — One Meta-Model to Rule Them All
23mThe two types of state management
27mCrafting state management – A principle based architecture
52mState management beyond the libraries
45mArchitectural Thinking on Flutter State Management
30mManaging State Management
24mPanel discussion about state management