Handling database requests

I'm not disputing the use of user cookies for authentication

TL;DR

The user is asking about handling database requests and whether they should use separate functions or one function for different queries. The response states that it depends on their specific needs and use case. They also discuss the possibility of clogging up GitHub with multiple repositories. There is no specific solution provided in the thread.

Then what's the issue? 😅

If you mean setting permissions, as said previously, you should use a function

If that's the issue, yes, you can prevent people from creating documents by only giving read permissio

Respect calls to a function, they're rate limited by default, but you could implement custom rate limits inside the function if you need even more strict limits.

I will yeah

I presume functions requests to database completely override any permissions, like a super-user?

Which means I can remove the user create permission?

Yes, you need to set an API key in the function so they override permissions obviously

Yes

You only set permissions for the user to execute the function and nothing else

Apart from read permission

@D5 Just a quick question, I might've already asked it but for my functions, what's the best conventions to use? For example, should I:

Create a separate cloud function for creating documents, editing documents and deleting documents.
Create one cloud function for all database queries.

And additionally, should I be setting up the functions just as the create document function works with the Appwrite API or, should I make it case-specific (e.g: have a function called "Create Memo" and only have arguments like "content" and "colour".

Yes
This depends on your needs

This latest ones depends on your use case too and preferences, but most times I prefer having separate/custom functions for each thing

I just didn’t want to clog up my github with a bunch of repos but i guess we’ll see

In my case, the functions would all relate to the same database and collection

Of course you could handle everything with 1, but I think some cases it's not the most convenient approach mainly from a performance perspective. Also you don't need to use GitHub for functions.

As said, this is a bit complex topic since it depends more on your use case and specific needs

Maybe in your case it's 100% fine using the same function. If you're going to do the same or almost the same kind of thing or requests, but for example, with different parameters, then you will be fine with 1. However if you're going to do multiple and different things, then it's better multiple