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
- 1.9.5 Migration problem
1.9.5 migration problem after run migration command only openruntimes-executor
- Issue related to index
Why it is showing this error?
- Appwrite Sites deployment fails because ...
Appwrite Cloud Sites deployments are failing consistently for both GitHub and manual deployments. The build command completes successfully and packaging also c...