Remind me not to showcase my apps to you xD

It’s quite capable, and the docs are decent. The integrated AI assistant is also quite nice. Plus, publishing native mobile via Capacitor is reasonably well documented. That said, I haven’t actually built anything with it myself.
99.5% uptime works out to having an outage of 7 minutes every day of the year, on average. Some folks may not really notice that but a lot of serious businesses simply cannot tolerate that unreliability. It’s unfortunate ![]()
This is such a bizarre post - extra so because you’re the community manager. You can’t see why people are routinely getting a vibe check as to whether they should abandon this platform? That they are questioning the decision to continue investing time into a proprietary system - the skills and products of which don’t transfer to re-building their application anywhere else? You see people audibly wondering if they should head for the exit like @keith and other ex-Bubble diehards and ask the rhetorical equivalent of “why is everyone whining?”
Wild.
Give me a self-hosted containerized version of Bubble, and I’ll be all over it like flies on…uh…bananas…or whatever. ![]()
Update from Josh:
Just imagine what @vini_brito is brewing up ![]()
Alright guys, that’s it. I’m staying but who has been running them expensive queries huh? Those must be some crazy operator chains and whatever else ![]()
Exactly. How do we know that they are all related? And even so a DoS attack doesn’t really indicate that someone wants to disrupt Bubble very badly; it primarily indiciates yet again that Bubble didn’t properly build its archtiechture (just like the cache issue or the rollback issue which are all big red flags regarding Bubble’s architecture and it ability (or willingness?)to build properly.
Finally, it’s not like this a one-off. The last major outage unrelated this week’s downtime happened just 10 days ago! ![]()
And while that occurred before you joined, it wasn’t exactly ages ago…
You manage all of this as a solo developer?
What if we run a redundant site on a separate no-code platform in the background. Connected to and synced with your main app by api . Then when a disruption happens the app automatically redirects traffic to the backup app until the disruption is over. The users never know. At the end of the day, if you are in business, you are responsible for your own risk management. Moving to another platform completely doesn’t remove the risk completely. You have to manage risk in your own systems. I’m a non-technical developer with a background in finance and risk management. I am legitimately asking what everyone does to manage platform risks which exist everywhere. Besides building out your own platform, with coded redundancies, before you are ready to scale like that.
True that about the user-friendly error message. The horrifying server error page from Cloudflare will chase all our customers away on a fintech platform. We defnitely had some sleepless nights last night @Bubble
I think Kieth left a while ago
Depends on which route you take - you can create ~1000 things in 7 seconds with the Bulk create API…
Sorry, shoulda prefaced that with I’ve not played with creating massive numbers of things since their bulk updates at the time we were using bulk but it was like 2-3 yrs ago.
For recursive it’s still just as slow and unreliable though I believe
You need to try these out on their new plans ![]()
Can confirm uploading via the bulk uploaded is blazing fast.
I uploaded 3000 records in less than 45seconds and part of that was a recurring backend workflow with a 5 second wait
![]()
Is he still supporting his plugins?
I don’t think so. From what I can see this is his last post
Very sad