Need Help on Moving to an External Database for High-Volume App

Hello Bubble Community,

I’m looking for some guidance and insights regarding a database migration for my application, which handles a high volume of data. Here’s an overview of my situation:

  • User Base: Currently, we have over 80,000 users, and the user count is projected to grow significantly in the coming months.
  • Application Setup: I have three interrelated apps sharing similar data. This number may increase as the application evolves.
  • Data Volume: The nature of the app involves handling a lot of data, so data volume is high and will continue to increase.

Given these factors, I am considering migrating our database to an external one to ensure scalability, performance, and data integrity across all apps.

I Need Help With:

  • Choosing the Right External Database: Based on the nature of my app, which database would you recommend? I’d love to hear your reasoning behind any suggestions.
  • Pros and Cons of Moving to an External Database
  • Community Experiences: If anyone has previously migrated their database from Bubble to an external one, could you share your experiences?

Any advice or insights would be highly appreciated!

Thanks in advance for your help!

1 Like

Hmm :thinking:

Good question.

I hear a lot of good things about Xano and we are currently transitioning to it on one project due to HIPPA regulations. This seems like a great ‘no-code’ option for a lot of people.

We have also used AWS, but it is far from ‘no-code’ friendly.

It really depends on your skill level with code and how much work you want to put into learning it.

What is the reason that you have 3 apps with similar data? Why not just use one app? 80,000 users is a great success! Congrats! I hope it keeps growing for you. :tada:

Also, are you concerned that Bubble can’t handle that amount of data? I have seen Bubble have millions of records in the database and work just fine. It really just depends on how you build it. :blush:

1 Like

Thanks for your response, @J805.

The reason we have three apps is to cater to three different user types, each with distinct actions. Some tables are shared across all apps, while some data is unique to each app.

I’m considering moving the database externally to avoid data discrepancies between the apps. I also believe this move will improve speed and performance.

We’re planning to transition our high-volume app to an external database to handle increased data loads more efficiently. If anyone has experience with this type of migration, I’d love some tips! Specifically interested in advice on choosing the right database, handling data replication, optimizing for performance, and ensuring minimal downtime during the switch. Any best practices, tools, or challenges to watch out for would be incredibly

1 Like

Hmm :thinking: Interesting. Most of the apps that I have built with different user types would still be in the same app. Sometimes they might have a different page in the app, but they all use the same database and just have a ‘user type’ field on the user data type. We just make sure privacy rules are set up properly and page redirects are in place to make sure the user sees the right information for them.

I am sure you had your reason to making separate apps, I would be curious to look at it and see how you guys handled it. :blush:

@anoboy712 My suggestion would to use this :point_down:

For the transition, I would suggest saving in both locations until you are ready to make the switch. That way, it will be in sync and you can do testing without it breaking what you already have. Then when you are confident in it working, you can make the switch. :blush:

Also, welcome to the Bubble Community :tada: :confetti_ball: