Crafting state management – A principle based architecture
summary
Includes a concrete meta-model with six sections that maps commands, computation, storage, derivation, events and consumers and uses it to compare ngRx ngxs akita redux-observable Redux and Flux. Recommends push-based architecture, a single normalized serializable store, immutable state, pure functions, restricted concurrent updates, facades and a separate derivation layer. Claims these specifics produce reproducible state and enable time‑travel, undo/redo, optimistic updates and much easier debugging.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:15CRAFTING STATE MANAGEMENT - A PRINCIPLE BASED ARCHITECTURE
- 3:19Storage
- 4:16Store state as one single piece
- 6:40Transformation
- 13:15One direction for data
- 14:26A separate layer for state derivation
- 16:22Encapsulate commands into objects
- 17:48Provide commands/events in a single stream
- 18:56Hide details behind a facade
related talks
18mState Management — One Meta-Model to Rule Them All
41mManaging State in Angular Applications
25mAngular Architecture: From Patterns to Implementation
23mState management with ngrx
43mState Manager Architecture
30mState Management Patterns and Best Practices with NgRx
41mThe Battle of State Management in modern frontend applications
22mState Management Techniques and Family Therapy