One school has workspace licence. They want to build an app for staff and students attendence in Appsheet.
They will be retaining data for atleast 3 years. And rows may exceed 500K .
Security Filters may be applied.
Nearly 500 users (teaching and non teaching staff) will be using this app.
Is Appsheet the right choice?
Is there any other alternatives for it?
Just my opinion…I would say that economically, yes. And you would need to archive unnecessary data on another location.
I’d suggest multiple apps accessing the same data. For instance, you will have people who will ADD rows to the dataset and you will have people who need to view aggregated data/charts etc. The people who ADD rows do not need to have access to the 500k rows that will accrue over the 3 years. That’s how I would make the apps stay performant.
Also use Looker to do all the charting and so on rather than build in App dashboards for that much data.
My friend @jaichith you can do it with Appsheet. Only you have to Scale your app with Partitioned data across many files.
Please take a look the following documentation:
I think it’s the right choice
500 k records with multiple tenant with single app. Only a solution to ensure the response speed (sync speed) to comfort the app user is to host the data with Cloud SQL with the perfect tune. With that, AppSheet is perfect solution.
But the school would need Enterprise Appsheet for the CloudSQL part. I doubt that would happen based on 500 users.
I’m just saying from technical point of view.
As they are using Workspace with Core, they are not able to use either partitioning or real databases. With 500k rows in 36 months, it would mean 14k rows in one month. If you keep 3 months data for teachers, admin etc. in another app., that should be enough for them and the performance should be good as well (though if you don’t have heavy virtual columns).
I believe while developing attendance and timesheet apps that depend on users logging in time from their own devices is planned, the app creators need to take a close look at the following post to know 'dos and dont’s with timesheet time capture with AppSheet."
This post has been participated by many AppSheet experts.
Exploring data partition
@AleksiAlkio @Koichi_Tsuji @scott192 @Suvrutt_Gurjar
I have seen this information in Appsheet site. My question is how many rows Appsheet can handle to the maximum?
EnterprisePlus
200,000 rows per AppSheet database
Unlimited AppSheet databases (200 databases per user)
I have planned like single ERP… But your idea may increase the developer workloads . But has phenomenonal benefits. I will explain to the client.
I have seen this information in Appsheet site. My question is how many rows Appsheet can handle to the maximum?
EnterprisePlus
200,000 rows per AppSheet database
Unlimited AppSheet databases (200 databases per user)
Is it not possible to have 500K records/ rows in single Database?
For every month should I change?