Bubble suitable for very large databases? (>46,000 entries and growing)

Hello,

I am working on a database for which I would like to create an app in which the existing data can be displayed, searched and filtered.

The database has a very simple structure, but the problem is its size: at the moment there are 46,000 entries and it cannot be ruled out that there will one day be around 100,000.

Is Bubble even suitable for such a task? If this is the case, I hope that you can give me some general recommendations on how to solve this problem.

So far, this database only exists as an Excel spreadsheet.

For very rapid database searches I use Typesense integrated with bubble. It’s cheap - like $10 a month.

Your app speed varies based on your build practices, UX, and privacy rules. We have apps with millions of rows of data. 100k will be totally fine.

1 Like

Thanks for your answer. However, I assume that the resulting costs would be considerable and, above all, incalculable for me.

What costs? (Bubble doesn’t charge based on database storage)

1 Like

Well, I’ve been told this: “as the data grows more, the filtering and database operations will become more complex and will cost more WU than before”

Well, I don’t know who told you that, but having a larger database doesn’t increase WU, so that’s incorrect. A larger database might be slower to search through, but database size has no direct bearing on WU.

On a side note, I definitely wouldn’t consider 46k, or even 100k, to be a ‘very large database’, I’ve built and worked with apps in Bubble with databases in those ranges have have never noticed any real issues with performance.

1 Like

In fact the person how answered to my question replied: “It is but as the data grows more, the filtering and database operations will become more complex and will cost more WU than before. However, if you’re working with lots of data, I recommend you use Xano as your database with bubble. The response times are fast and you can perform complex queries and data manipulation.”

Another person said: “I personally have a few tables over 20k rows on Bubble databases and the WU are getting pretty high (couple million a month).”

Other people agreed that Xano (or Supabase) wouldbe a good choice with Bubble. Any ideas about why I should use those?

I’m lost about the WU cost thing.

Then they don’t know what they’re talking about.

WU is a function of traffic/usage, NOT database size. WU for two similar apps with 10k rows and 1 mil rows respectively would be almost the same. They probably have an inefficient database structure or workflows…

No, if you’re primarily using an external DB and using Bubble as a frontend, you don’t use Bubble, because Bubble is shitty as a frontend because that’s not what it was built for. Bubble is good because of how the UI, logic, and database all link together.

4 Likes