compare use Bubble internal DB and switch to use DB on API Connection ( not the bubble SQL connector )
Would it be a significant reduce in WU unit? especially on apps performance alot searches on DB.
compare use Bubble internal DB and switch to use DB on API Connection ( not the bubble SQL connector )
Would it be a significant reduce in WU unit? especially on apps performance alot searches on DB.
Depends on the app, but if using an external DB, Bubble isn’t the best low/nocode platform.
@georgecollier but it is less consuming doing API calls than querying Bubble database right?
That’s why lot of people pairing Bubble with Xano or Supabase
@zhihong0321 how many tables you have?
You could move only the table that is consuming more WUs into an external database
Yeah of course, but if you’re heavily relying on an external DB, Bubble objectively isn’t a good front-end builder and other options are better.
Bubble’s an average backend, and an average front-end, but a great fullstack tool.
Yeah, agree with how you described Bubble there!
I found myself in a situation where I learned Buildship for the backend but I don’t want to learn a new frontend yet, so I remain with Bubble.
I think moving the table that consumes the most WU’s to an external database is a good approach though. You can keep the tables synced with a CRON job that run every ‘x’ time for example
Well said