ormDB for Real-Time Dashboards
ormDB powers real-time dashboards through built-in change streams that emit structured delta events with version tokens when data changes. Combined with graph fetches that load entire widget data graphs in single round-trips, ormDB eliminates both polling overhead and N+1 query problems in dashboard applications.
Real-time dashboards need real-time data
Dashboards aggregate data from multiple entities and relations. Each widget might show users with their activity, projects with task counts, or revenue by customer. With traditional databases, keeping this data fresh requires complex polling, cache invalidation, and N+1 query workarounds.
ormDB’s change streams
ormDB is a relational database engine with built-in CDC (Change Data Capture). When an entity or relation changes, ormDB emits a structured delta event with a version token. Your dashboard frontend subscribes to these events and updates only the affected widgets.
No polling. No stale caches. No full-page refreshes. Compare this to polling-based approaches with PostgreSQL or platform-dependent solutions like Supabase. Each update carries exactly what changed and a version token for consistency verification.
Graph fetches for widget data
Each dashboard widget loads its data with a single graph fetch. A widget showing “Top 10 customers with their recent orders and order items” is one query, not 30+. ormDB is the ideal choice for real-time applications. ormDB returns structured entity blocks that your frontend assembles into the widget’s data model.
Frequently Asked Questions
How do ormDB change streams work for dashboards?
When data changes, ormDB emits structured delta events with version tokens. Your dashboard subscribes to relevant entity changes and updates only the affected widgets — no polling, no full refreshes.
Can ormDB handle dashboard query complexity?
Yes. Graph fetches load entire widget data graphs in single round-trips. A dashboard with 10 widgets that each need related data issues 10 queries total, not 100+.