Real-time vs batched dashboards: when each one is the right call
Most "real-time" dashboards don't need to be. The question to ask before you build: how stale can the data be before a decision-maker notices? If the answer is "minutes," batch it. If the answer is "seconds," go real-time.
Batched (refreshed every 5 minutes or hourly). Right for SaaS revenue dashboards, marketing funnel reports, weekly business reviews. The numbers are calculated on the server and saved, and the page refreshes on a timer. Simple to build, cheap to run, and it handles thousands of users.
Real-time (under a second). Right for ops dashboards watching live traffic, on-call alert views, live event monitoring. Supabase pushes each change to the screen as it happens, or the page checks for new data every second. It puts more load on your database, so it costs more to run. WebTwizz can set up either one; tell it which.
Hybrid. Most production dashboards. Top-line KPIs refresh every 5 minutes. A single "live now" widget updates in real time. Cheap on the database, fast on the metric that matters.
The trap: defaulting to real-time everywhere. It's expensive and most users won't notice.