How to Break Down an Existing Database in Bubble

Idea Implemented
1

Hi everyone,

I’m currently working on a project in Bubble and I have an existing database that I need to break down into more manageable parts. The database has grown quite large, and I want to ensure that it’s optimized for performance and ease of use.

Could anyone provide guidance or best practices on how to effectively break down an existing database in Bubble? Specifically, I’m looking for advice on:

  1. Identifying which parts of the database should be broken down.
  2. Best practices for restructuring the database.
  3. Potential pitfalls to avoid during the process.
  4. Any tools or plugins that might help with this task.

Any examples or step-by-step instructions would be greatly appreciated!

Thanks in advance for your help!

2

I will start from the workload units and see which page/workflows are calling out frequently and causing the most WU consumption.

That basically gives you an idea - which parts of the app (or database) need to be optimized and which don’t.

Once you figure out which tables need to be optimized, then export the DB and import it into dbdiagram.io, which will help you better visualize the database and its relationships.

Don’t forget to create a separate branch and then only optimize.

Ankur@ Nocodetalks
Helping Bubble Devs to build No-Code Products. Follow me on Twitter