
I implemented a simple feature where a user can track how much money he saved by taking a bus instead of driving with car. Currently, each time he drives with the bus, an amount is added to his savings. However there is no history of how that came to be. I would like to add this history.
My question is, should do a second request on the client side be done to add an entry into the history document? Or should I write an appwrite function that reacts to updates on the savings document and adds an entry to the history document?

Either ways can work, but it's better to do it in a function as when the option will grow you'll be able to achieve much more using function with Server level API rather then the Client level API.
A good rule of thumb is to think of functions as microservices that together are composing the backend for you.

Cool thx @Binyamin ✌️

[Solved] Should I use a function or write client code?
Recommended threads
- Error importing data after server migrat...
Hello, I recently purchased a new web server and when trying to migrate my data from the old server to the new (both self-hosted instances of appwrite on coolif...
- REST API does not work for queries
``` curl -X GET "https://cloud.appwrite.io/v1/databases/<db-id>/collections/<c-id>/documents" -H "X-Appwrite-Project: <project-id>" -H "X-Appwrite-Key: <key>"...
- deleteDocments is not a function
Hello. At the bottom of my project's console, in the footer, I have `Version 1.7.4`. However, when I run my server side function, I am told that `databases.dele...
