💾 Archived View for bbs.geminispace.org › s › Bubble-Issues › 7 captured on 2023-09-08 at 16:45:13. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-07-22)
-=-=-=-=-=-=-
One server does not fit all, and in any case, the Bubble implementation is not meant to scale to very large numbers of users. It would make sense to think about solutions where instances federate with each other.
In practice, this could be something as simple as the instances subscribing to each others' feeds, and allowing users to reference (and notify) remote users as well as local ones.
2023-05-13 · 4 months ago · 👍 Addison, deathbyindierock, norayr
Out of curiosity, what is it about the implementation that prevents scaling?
2023-05-14 · 4 months ago
For starters, it's written in Python, which makes it inefficient for both CPU and memory use. Fortunately, GmCapsule has multiple worker threads (20 shared by skyjake.fi and geminispace.org), so it shouldn't fall over immediately. There's a single simple backend database (MariaDB), with *all* the user data (file attachments and all).
I'm not expecting the user numbers to become so large that there would be need for load balancing or database replication for sharing the load.
It would be great to reuse existing Gemini infrastructure for this. Antenna/Cosmos could be used as sources of "federated" posts that will appear in All Posts as new entries, to be interacted and commented on. Something to consider...
2023-05-15 · 4 months ago
I think this is potentially bigger than a simple feature for Bubble itself. I would love to see a community drafted specification for how to federate servers, much like ActivityPub but obviously designed with light weight in mind. But like AP in that it could be a generic way to federate different types of servers, not just bubble. Something as well defined as Gemini itself, so that implementation in any language would be straightforward.
2023-05-19 · 4 months ago
🐞 Mentioned in [#92] Multispaces
2023-06-19 · 3 months ago