im about to publish my SaaS Tool in about 2 Weeks and im a bit concerned about how the increase of Data could affect my Automations.
Im Providing a Linkedin Automation Tool where User can Upload a List of Contacts. On Average every User will upload 5-10k Contacts.
Users will be able to create campaign and sequences to automate linkedin actions.
For every Campaign one Lead at a time will be chosen from the Leadlist with a specific Status to Trigger an Action.
With an increase of Users the Leadlist can rapidly increase to 1mil (50-100 User approx.)
Back to my Main question. Do you think bubble is able to process such a large list in the backend without any noticeable performance issues for the users or would it be better to work with an external database?
I use Bubble for my clients still, but personally I have been using other solutions just because I have different requirements. Not saying I won’t ever use it personally, just like what I have going.
This is not about performance, it is about cost. The cost to have 5-10K contacts, which I believe gets transformed into a ‘contact’ for a Campaign to be selected one at a time to make a change to the database for their status followed by another action to likely use Linkedin API to do something, you will have at least 1.2 WUs (make change to thing and API call) per ‘contact’ so if you consider this happening for every User list, which you say can become 1 million 'contact’s at a minimum you are looking at 1.2 million WUs just for this, and that is assuming you run a campaign only once a month…now what would happen if you did it weekly?
Bubble Pricing of WUs is what makes this not feasible in Bubble, not the ability of it’s database to handle large amounts of data.
Good Point. Didnt think about the WU Aspect yet. I will try to test this out for know and will track the WU Usage. If its too high i have to think about pivoting to other solutions
