Database Architecture Concerns
Hello convex team. Currently im working on a new SAAS application and its main feature allows users to post data to my public api and store data for them to view later. In theory i want users to be able to store thousands of rows in my database for them to query later, however I was thinking would this not be bad for convex later on? Because each users data does not need to be synced with each other (always). Idealy, I would want a master database where the auth user data is stored, and other things. But users specific data is stored in there own database (table in this case) where each user (s) can only see there data.
Im not sure if convex can do something like this, im concerned that in the future If i have a lot of data, it will slow down other users accessing data because the data stored will still need to be parsed from top to bottom in the querys. Just looking for some advice, I love convex as a datavase but im not sure If its the best at my needs for this project. Vs something like sqlite where If i wanted more databases, I could just make another file and have user data separated from each other completely and not have other user data effecting performance (reads / writes ) of others
Im not sure if convex can do something like this, im concerned that in the future If i have a lot of data, it will slow down other users accessing data because the data stored will still need to be parsed from top to bottom in the querys. Just looking for some advice, I love convex as a datavase but im not sure If its the best at my needs for this project. Vs something like sqlite where If i wanted more databases, I could just make another file and have user data separated from each other completely and not have other user data effecting performance (reads / writes ) of others
Join the Convex Discord! Explore Convex, the backend platform that keeps your app in sync.
15,550Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
