Caching woes
Hello, I have a question regarding Convex. I'm exploring its use for an internal app for approximately 3000 staff members. My understanding so far is that caching appears to be limited to a user's session if
However, since the entire application is behind a login, I anticipate that I will largely not benefit from caching, despite having a significant amount of shared data among staff.
My current thought is that the only solution would be to move all queries to the server, perhaps by using a stable argument like a secret. Is this understanding correct, or are there alternative approaches to leverage caching for shared data in an authenticated environment?
ctx.db.authctx.db.auth is called. However, since the entire application is behind a login, I anticipate that I will largely not benefit from caching, despite having a significant amount of shared data among staff.
My current thought is that the only solution would be to move all queries to the server, perhaps by using a stable argument like a secret. Is this understanding correct, or are there alternative approaches to leverage caching for shared data in an authenticated environment?
