How well does it do with larger databases?

[D1G1TAL137]

Hello

Has anyone used Budibase with larger databases? How well does it do? (Self-hosted)
I expect the database to have around 300,000 rows in a year across 3 tables with some relational columns. I've attached a diagram to to roughly show the structure, from what I know Budibase is not a true relational database that is why I am curious how it handles them in larger amount?

(Also want to use Calculation Table on all of those as well. )

Basically my question is: Will BudibaseDB be able to handle that many rows and relations. And if not, would using Postgres do, or is Budibase just not build for larger databases?

Thanks

[benaunt]

We have a Budibase app with +30 tables and hundreds of thousands of rows built off of MSSQL as the backend DB. Its used by a team of 15 users as their key system throughout the day.

We have the app working reasonably well. As your DB structure is quite simple i don't envision you will have much issue.

For us:

• We had to put effort into optimising our screens, tables, queries, looking at the browser consol to see what data operations were taking time etc. It would be nice if the product had more internal mechanisms to do this.
• We had to be careful were we used Budibase internal relationships based off our MSSQL structure
• We had to use Budibase views of our tables to control what relational data loaded rather than just displaying a table
• For more complex data views, we used queries directly from SQL rather than Budibase. Unfortunately, you do lose some of the automatic UI elements doing this (infinite scrolling etc)
• We had to ensure we did not load large amounts of data by default, using filters etc.
• We ended up removing the use of relationship pickers and opted for option pickers with data providers. So we could control exactly what data was being returned. This one is a bit annoying as relationship pickers "just work" whereas option pickers used in this context require more effort.

The key issues:

• Form relationship pickers - no ability to optimise or control in anyway so will slow down as more rows/relationships off a table are defined
• Dynamic filter component - similar to above

This app is on a Budibase instance that has several other applications in use by other teams.