Custom rate limit for database collection access per user

Hi, what do you think about adding custom rate limits to database collections? Current Problem I created a for loop that writes 10.000 entires to a database, with a single field: The Appwrite instance went offline for about 3 minutes to handle all those requests. (The server, where my Appwrite instance is running on, has 16GB of RAM and 4 Cores) All those 10k entries are now in my database. Current Solution Currently, we could call a Function, which does the rate limiting. The problem with that is, that the current implementation of Functions, spawns a process every time the function is called, which uses a lot of resources and takes its time, as discussed in #1261. Handling rate limits via Functions would definitely also bring the server down, on such an amount of requests. The bad part is, that nothing is preventing a harmful user to do exactly what I did. Possible Solution So let's say that we have a collection named posts, and we'd like the …