Caching Solutions?
I'm creating an audio transcript app for audio that is typically about 2 hours long. When I get the transcipt, it is in a form chunked by speaker, and I put each chunk in a convex table. No problem from the ingress perspective, but when viewing in the web, I blow away the free tier of DB Bandwidth pretty quickly. This wouldn't be the case if this data was cached in the browser (can't wait for the local-first sync solution). The data comes in over websockets so it doesn't get cached and if I reload the page or load another transcript, it just gets the data again from the DB. This data will never change once it's written to the DB. The only caching solution I can think of is to move this query into an HTTP Action and let it get cached like any other http response. I am posting here to hear from other folks who have contended with this and have caching solutions to reduce DB bandwidth.
Join the Convex Discord! Explore Convex, the backend platform that keeps your app in sync.
15,138Members
Resources
Similar Threads
Was this page helpful?
