Feeling lost with the backend issue

I encounter a problem of slowness in the app (due to the size of the database) and as I see the only solution is to move the backend to an external server.
The problem is that it is complex because of the api’s that is connected to the app.

Has anyone encountered this and found a simple solution for people without a technical background?
thanks

Hi

Can I know the current size of your database? This would help me put a workable limit on the Adalo internal dB. I do not expect more than 5000 users for the first app version. If its gets larger then I might needs to think of alternates.

There are thousands of units in the database, the order of magnitude of the users is not large, but when there are several dozen users using the lists that exist in the app at the same time, the app moves very, very slowly.

To fix app slowness from a large database, optimize queries, use managed services like AWS RDS, and add caching with Redis. Platforms like Firebase or Airtable offer easy backend solutions, and tools like Zapier simplify API connections.

@james.crennan talked about the possibility of choosing more powerful servers (if I understood correctly). Maybe if there was more information on the subject I could avoid the procedure of manually transferring the app’s backend.

1 Like

@nadavma2 can we get on a call? I’d love to look at your app and the DB. We can certainly upgrade the DB, but I think we can get significant performance improvements from a host of other things, especially indexing your DB. Can we take this to email? james.crennan@adalo.com

1 Like

Of course, I already wrote you an email.:pray:

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.