I enjoyed your article and your thoughts about the dangers/challenges on data caching. Good stuff.
Redux, however, is more than just a front-end caching mechanism.
The purpose of Redux is to (a) separate UI and business logic using event/action delegation, (b) centralize state changes code, and (c) encourage 1-way data flows.
Equally important as state management is the concept of sharing state. How to share data and push state changes is the most challenging part... one where Redux solutions fail IMO.
MobX, Recoil, and Akita are all current/upcoming solutions that address the challenge of pushing changes and notifications to data consumers (aka observers).
I enjoyed your article and your thoughts about the dangers/challenges on data caching. Good stuff.
The purpose of Redux is to (a) separate UI and business logic using event/action delegation, (b) centralize state changes code, and (c) encourage 1-way data flows.
Equally important as state management is the concept of sharing state. How to share data and push state changes is the most challenging part... one where Redux solutions fail IMO.
MobX, Recoil, and Akita are all current/upcoming solutions that address the challenge of pushing changes and notifications to data consumers (aka observers).
Check out my articles on medium.com/@thomasburlesonia; perhaps these will provide value-add to your insights.