Event-Sourcing your React-Redux applications
summary
Claims that replacing CRUD with an append-only event store gives full auditability and easier concurrency for a permit-to-work app, implemented with React + Redux reducers and actions, a command service that writes events, and a projection database for optimized reads. Real-time updates use socket.io/websockets. Demonstrates event immutability, reducers rebuilding state from events, and that projections plus Redux keep the UI fast and predictable; shows the pattern implemented end-to-end.
AI-written summary · about
chapters (12)
- 0:00Event sourcing and React-Redux
- 2:29Why event sourcing matters
- 7:11Traditional storage limits
- 10:34Commands and CQRS design
- 18:39Problem with current state only
- 20:29Bookkeeping and event history
- 23:27Event sourcing and database design
- 25:17Event sourcing with projections
- 31:05Real-time updates with WebSockets
- 35:22Projections for querying
- 37:07Integrating with React-Redux
- 39:23Q&A
