I am making a learning app that I want to be able to scale to around 25k users.
Most of the content in the app, users will be interacting with passively so performance wise, there shouldn’t be a problem (tables (for example courses) will have only a few thousand items max). Also, for security reasons, any content people add will have them as a row owner so they will only download their own data.
However, I have one Table (Task fulfilmments) in which users themselves will generate a lot of items. A few hundred to a few thousand per user.
The logic thing would probably be to make this Table to be a Glide Big Table. However, I am missing some functionality (rollups against relations, search in computed columns etc) which still leads me to using normal Tables.
My question is: given that I use row owners for any content created by users, will a normal Table be able to scale to hundreds of thousands of entries (because each user will only download a small fraction of that), or will everything go bonkers and should I use a Big Table, thereby losing some functions.
I should note that I have one admin account which can see anything, I can imagine using this account will become impossible once there are too much entries in the Table?
Rollups against relations (and queries) are now supported in Big Tables, as long as the target column in the Big Table is not a computed column.
The answer to this question is kind of moot, because there is no Glide Subscription Plan that currently supports this. The extended row limits that you get with Business and Enterprise Plans is only for Big Tables. For all other data sources, the row limit per project remains at 25k. I don’t think that’s currently enforced (at least not on Enterprise), but that doesn’t mean it won’t be in the future.