Taming Signals, or a BI System on Graph Reactivity in 2 Months
summary
Describes developing ReGraph, a new abstraction layer over Svelte Stores that records subscriber relationships as a graph to build an interactive dashboard constructor with widgets (filters, calendars, periods, charts, tables). The approach makes reactive connections manageable at runtime, is applicable to other frontend frameworks that use signals or similar primitives, and was built to enable a BI system within two months and to be reused in other interactive projects.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:50About me and Dalia
- 3:17BI system goals
- 5:51Tech stack
- 6:52Reactivity theory types
- 8:36Redux vs RXJS vs Effector
- 11:51Signals and reactivity role
- 12:32Svelte 4 and 5 reactivity
- 14:40Runtime state challenges
- 15:21Reactive graph system
- 16:24Prototype dev and testing
- 19:13Refactoring custom report
- 21:21BI system demo
- 23:48Saving widgets state
- 24:51Graph reactivity apps
- 25:33Reactive graph recipe
- 26:59Graph structure and components
- 27:46Conclusion
- 28:13Q&A
related talks
52mIt's Time To Talk About Signals
34mBeyond Signals
06mEmbracing Reactivity: Signals Unveiled in Modern Web Frameworks
40mReactive Programming: A Better Way To Write Frontend Applications
27mA Deep Dive into Fine-Grained Reactivity and the future of Signals
37mReactivity and Signals: Demystifying Frontend Magic
29mBuilding Web Applications with Signals at Grammarly
29mRevolutionary Signals