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
- Query Appwrite
Hello, I have a question regarding Queries in Appwrite. If I have a string "YYYY-MM", how can I query the $createdAt column to match this filter?
- Different appwrite IDs are getting expos...
File_URL_FORMAT= https://cloud.appwrite.io/v1/storage/buckets/[BUCKET_ID]/files/[FILE_ID]/preview?project=[PROJECT_ID] I'm trying to access files in my web app...
- Invalid document structure: missing requ...
I just pick up my code that's working a week ago, and now I got this error: ``` code: 400, type: 'document_invalid_structure', response: { message: 'Inv...