Going big with MobX
summary
Argues that MobX replaces Redux for a large React financial-analytics app and explains what was built: a modular windowed UI with per-module stores, real‑time feeds at 4 updates/sec, and about 20k lines of JS (30k with tests). Uses MobX v4 (notes on v5 proxy changes), mobx-react, devtools and low‑level atoms API to lazily subscribe so heavy views avoid creating ~30k subscriptions; it works after addressing observable-array quirks, decorator issues and async/debugging blind spots.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 1:25React and Redux problems
- 2:48EVS project overview
- 4:34Why MobX
- 5:56MobX: observable
- 7:03MobX: derivations
- 8:51MobX: reactions
- 9:53MobX: actions
- 11:14MobX data flow
- 13:01Strict mode and project structure
- 14:25State storage in MobX
- 16:12Reactivity and magic
- 17:16Performance optimization
- 19:21MobX for local state
- 21:08MobX v4 issues
- 23:16DevTools for debugging
- 24:20Rerendering problems
- 25:02State serialization
- 25:44Decorator issues
- 26:06MobX advantages
- 27:10MobX performance
- 28:58Performance examples
- 30:03MobX atoms
- 31:31Subscription optimization
- 34:40MobX State Tree alternative
- 36:47When to use MobX
- 37:30How observable works
- 38:12MobX and RxJS integration
- 38:53Async issues
- 40:24Debugging complex reactions
- 41:09MobX framework integration
- 42:34MobX version issues
- 44:17Common newbie mistakes
related talks
09mMobX - Performance and Sanity
25mMobX vs Redux: Comparing the Opposing Paradigms
26mStay Reactive with MobX
24mMobX; Hight Performance Library
37mApplication state management
28mMobX: The Journey
41mMobX, or: Going from Mutable to Immutable to Reactive State Management
59mMobX and the unique symbiosis of predictability and speed