Back
Whats best practise for Appwrite Cloud?
Appwrite Teams map very nicely to my needs, it is how i group users together. ... I use roles to define permissions. Should I also map a table to each team ? ... or have one big table? (seems crazy to me) Should I split ranges of such tables into databases? like 'tables with IDs starting with 0' , 'tables of ids starting with 1' ... etc.
Some groups of people will have lots of rows in the table, some will have a few.......
How would u do it?
Thanks, Tom
TL;DR
Developers are discussing the best practices for structuring Appwrite Cloud. One suggestion is to use Appwrite Teams to group users and roles to define permissions. The question is whether to have one big table or separate tables for each team. A proposed solution is to split ranges of tables into databases based on ID ranges to manage different loads efficiently.