Back

I also faces the same problem. Use supabase. It has some learning curve but it's worth it.

Its designed in a way that you end up being over dependent and its hard to move backend elsewhere without trading off the ease of firebase as backend

Are you using firebase as a backend DB ? very few things you can do. Optimise queries, implement caching wherever possible. Implement data IO limits on in and out calls. Try to get free firebase credits via GCP startup program and such

Firebase is kinda mud Once you're in, there less way out Tried and tested when I was building my MVP It was adult app and blew up in a month But cost was such high that 60% of revenue was in fb

Is it firestore?

Change to some other database if possible.

Try appwrite is pretty good... It's open source and quite user-friendly

Use Firebase's querying capabilities to limit the amount of data read. Instead of fetching entire collections, fetch only the necessary documents or fields. Also regularly clean up and archive old or unused data. This can reduce storage costs and make your database more efficient.

Efficient data structuring can significantly reduce your read and write operations, which are major cost drivers. Consider denormalizing your data or using more efficient data models.

Find a tech partner

need some more info like how you query and how many active connections are there tell us about those parameters then we can suggest some improvements