Using events and modern sm tools to clean up local-first logic
summary
Argues for storing domain events instead of only final state so timelines, retrospectives and derived insights emerge from the event stream; shows that there is no npm package that fixes this and that it usually lives on the backend. Describes a custom sync engine that forwards events to other clients and backend and reports 200 milliseconds of propagation (200 milliseconds), a concrete engineering choice that produces noticeably smoother real‑time UX.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 1:57Imaginary to-do app
- 6:57Domain events in task management
- 10:28Event-driven architecture
- 12:19Learning from communities
related talks
21mEvent is the new Model
31mEvent Driven Frontends: What, Why and How
19mThe Eventful API: Rethinking Frontend State from the Server Down
44mHow to Approach Modern Web Applications
20mEvent Driven Frontends. What, why and how.
18mThe need for speed - Single-page apps, Optimistic UIs, Reactivity
01h 18mThe future of chat
57m🚨 Live On the Edge 🚨