First important point: you can continue using Bubble, it will handle your demand without any problems, however, you will probably have to migrate to a more robust plan or buy tiers to cover all the WU you will consume.
If you are not willing to increase your costs with Bubble, follow the strategy I used to save 97% of my WU.
Context
To give you some context, I have a system for sending mass messages on WhatsApp + a chat space that is also integrated into WhatsApp.
- Recording of each message that arrives on WhatsApp in the Bubble database
- API to send each new message via chat
- For each message sent, I have the following actions
- API call
- “Sending” record
- Update of the sending status in the table
Now imagine, more than 200 clients, where each client sends more than 1000 messages per day. My WU cost would be very high.
Solution
I started using Bubble only as a front-end.
I installed N8N and Supabase on a VPS and now I have:
- All my logic flows occur within N8N and no longer in Bubble.
- All my records are made in Supabase and no longer in Bubble.
- I have Supabase synchronized in real-time (RT) with Bubble to respond to RT in the chat.
Suggested reading
I wrote a article that is going to teaches how to do the RT between Supabase and Bubble
(How to configure real-time between Supabase and Bubble.io)
1 Like