Document listener limitations?
I'm looking at using Convex for a project that would have a few thousand concurrent users listening to a handful of documents that would update at a max of 1 time per second in bursts, as a statistics dashboard for a live event. Are there any limitations I should be aware of that might cause issues for this use case? I didn't see very much about concurrent listeners in the docs.
I'm asking because a lot of similar services have really low limits (like 200 listeners max) and we're currently using Firebase, but would like to move off of it eventually.
2 Replies
We have customers who have a large number of concurrent connections (e.g.: https://t3.chat/). We don't explicitly limit simultaneous connections.
If you have a simple query whose contents only update once a second, you can probably take advantage of the automatic query cache to reduce database bandwidth: https://docs.convex.dev/functions/query-functions#caching--reactivity--consistency
T3 Chat
T3 Chat - Advanced AI Assistant & ChatGPT Alternative
Access premium AI models including GPT-4 and Claude for just $8/month. Free tier available. The smartest AI assistant for work and creativity.
Queries | Convex Developer Hub
Queries are the bread and butter of your backend API. They fetch data from the
Awesome, thanks for the info. I was aware of t3 chat, just unsure of whether or not there we weird limits on the number of listeners for a single document (some other providers have weird limits!), but that sounds perfectly good to me.