Will splitting categories into their own databases slow down my app

Need help Database
1

I’m considering breaking up my current large database into separate databases by category, as each has its own unique field. I’m also concerned that the single database may become too large over time. I’m planning on having 15 separate databases, each with its own front-end popup input and repeating group to display the data. Are there any potential issues with this approach, such as the possibility of slower app performance?

Thanks

2

Hi @GeorgeCantCode

Using multiple databases in your app can be a good way to organize and manage your data, especially if each database has a specific purpose and its own set of unique fields. However, there are a few potential issues to consider when using multiple databases in your app:

  1. Performance: Splitting your data into multiple databases may result in slower performance, especially if your app has to perform a large number of queries or if the databases are very large.
  2. Data integrity: If your app needs to use data from multiple databases in order to function properly, you may need to carefully manage the relationships between the databases to ensure that the data is consistent and accurate.
  3. Complexity: Using multiple databases can make your app more complex, which may make it more difficult to develop and maintain.

Overall, the decision to use multiple databases in your app will depend on the specific needs and requirements of your app. If you do decide to use multiple databases, it’s important to carefully consider how the databases will be used and to optimize your app’s performance as much as possible.

3

Thank you for your response. I appreciate your advice and will carefully weigh the pros and cons of this approach before making a final decision. Thank you again for your help!

1 Like
4

You’re welcome @GeorgeCantCode Happy to help you. :slight_smile: