Event-Sourcing your React-Flux applications
summary
Argues that React and Redux apps gain auditability and resilience by pairing CQRS with Event‑Sourcing, showing commands with unique IDs, event storage, and projector services that push updates via websockets; demonstrates a permit workflow, reducer wiring, and how projections live separately from the event log so queries stay fast. Claims include stores events instead of state, commands become validated actions with past‑tense events, and projections rebuilt from events to recover or add new read models. Implementation details and wiring are concrete and repeatable.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:01(Semi) Structured storage
- 5:56Command Query Responsibility Segregation
- 7:07The JavaScript command
- 8:30A Redux Action Creator
- 14:36Event Sourcing
- 16:47Event Pushing
- 17:56React with Redux
- 21:28The permit collection reducer
- 22:18The single permit reducer
- 23:10The React application startup
- 23:58Connecting the state to the component
related talks
49mEvent-Sourcing your React-Redux applications
07mWhy React is Eating the World
43mUnraveling the Threads: Event-Sourcing, CQRS, and Event-Driven Architecture
43mEvent driven development
54mThinking in Events
44mReactive Applications with Event-Sourcing and Server-Sent Events
50mAn Introduction to CQRS and Event Sourcing Patterns
01h 05mDDD, event sourcing and CQRS – theory and practice