jsonb-analytics-snapshot

Pre-aggregated analytics data can be stored as a JSONB snapshot in a single document to enable fast dashboard reads. This pattern persists the metrics payload, serving it on subsequent requests without recomputing historical aggregations.

You can scope data by studio and optional user within defined periods using periodStart, periodEnd, and periodType. This approach aligns historical data into time-bounded snapshots like daily, weekly, or monthly intervals for precise analytics.

Lazy evaluation for JSONB analytics snapshots computes the metrics payload only when a requested snapshot is missing. After generating the pre-aggregated data, it persists the JSON document to serve all future dashboard requests instantly.

Yes, Prisma can store pre-aggregated JSONB metrics payloads for dashboards. The JSONB Analytics Snapshot pattern leverages this stack to persist computed analytics documents, ensuring high read performance for immutable historical data.

You need a JSONB snapshot pattern for analytics dashboards requiring aggregation of historical, immutable data where high read performance is critical. It bypasses heavy runtime calculations by serving pre-computed metrics payloads directly.

Pre-aggregated JSONB snapshots are limited by their immutable, time-bounded nature. Once a snapshot is generated for a specific periodStart and periodEnd, it does not automatically update, making this approach unsuitable for real-time or frequently changing analytics data.