Cloud Function for all Use-Cases or Serperate for Client App
- 0
- Flutter
- Tools
- Databases
- General
- Self Hosted

Since I will have the client app of Flutter for data-input and NextJS for dashboard and reporting - starting from Flutter first. So I want to have one api routes for both of them to connect to appwrite.
After some communication, I can create cloud function to handle the api routes, plus hono to create one deployment for all use cases ( similer to api projects). so my question is, having multiple uses case in one deployment, will the cloud function be slow and any issue with that. The other option is to create the function for Flutter and also NextJS later.
Please give me some suggestions or ideas to effectively use. Thanks

Didn't you have another thread on the same topic? 🧐

to make it more specific topic 🤣

One function is fine. Just make sure each execution finishes as fast as possibly

which means if the function is requiring some time to finish. and there are many requests. it will have issue. correct me if I am wrong

Possibly. That depends on the language/runtime.
It's more so the longer an execution runs, the more likely it will be timed out or killed

thanks. whata would be ideal language/runtime for this case as suggested by you.
Recommended threads
- Appwrite custom domain verification fail...
So I've left enough time for the records to propagate and I've tried adding in a subdomain for the appwrite endpoint so as not to cause a clash with two CNAME r...
- Offline replication with RXDB
Hey there! Trying out apprwrite with rxdb for an offline focussed application. I cannot seem to find on how to set the permissions on a per document level?
- How to Fetch Item and Include the User/A...
A typical workflow with ORMs is to, for example, fetch an item from the DB and include the user who created it. How would I do that with AppWrite? Is that easil...
