Event Driven Frontends. What, why and how.
summary
Brings raw business events into the browser, fetches per-customer daily event logs plus snapshots, loads them into a WASM SQLite stored in OPFS, and runs SQL in a web worker to build reports client-side. Uses snapshotting to shrink huge logs, initial downloads often tens to low hundreds of MB compressed (some customers <20MB, edge cases near 500MB), avoids backend aggregation costs, needs reasonable hardware (~16GB RAM recommended, browsers hit ~4GB memory limits), and uses the sqlite.org WASM npm build.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 1:51Why event-driven frontends
- 5:44Bringing data to the browser
- 9:57Event sourcing in the browser
- 13:52Storing data in OPFS
- 16:40Benefits and trade-offs
- 18:30Q&A
related talks
31mEvent Driven Frontends: What, Why and How
13mUsing events and modern sm tools to clean up local-first logic
21mEvent is the new Model
47mPatterns for Building Event-driven Web & Mobile App Backends
29mThe Design and Evolution of Event-Driven Databases
19mThe Eventful API: Rethinking Frontend State from the Server Down
47mEvent Driven UIs
39mFrom Event-Driven to Automotive