Best practices for handling aggregated metrics and intermediate tables in Convex
We’re using Convex as our main database, and as our app grows, we’re starting to store a lot more metrics and analytics data (things like usage stats, event counts, and performance tracking).
Right now, we’re building intermediate tables with precomputed aggregations to keep queries fast — but it’s getting harder to maintain as the dataset expands.
I’m curious how other teams using Convex approach this:
Do you store and aggregate analytics data in Convex directly?
Or do you offload metrics to an external system?
Any best practices or patterns you’ve found helpful for managing analytics efficiently?
Would really appreciate hearing what’s worked for others!
1 Reply
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!