Bluesky migrates to single-tenant SQLite
github.com
Bluesky migrates to single-tenant SQLite
1–10 of 247 posts
Re: Bluesky migrates to single-tenant SQLite
#2This seems like a very misleading title, the Bluesky PDS is the meant-for-selfhosting thing they distribute, not the bluesky service as experienced and used by most of its users.
Re: Bluesky migrates to single-tenant SQLite
#3I am curious, does the HN folks know if bluesky is more active than nostr or the mastodon network?
Re: Bluesky migrates to single-tenant SQLite
#4Interesting... I like the strategy of having each user be 1:1 with a DB. What would be done for data that needs to be aggregated across users though? If I'm subscribed to another user and they post, how does my DB get updated with that new post? Or is this meant just for durable data and not feed data (like profile data, which users are followed / not followed / etc.) and all the interactive stuff happens separately?
I like that "connection pooling" is just limiting the number of open handles in a LRU cache. It's also interesting because instead of having to manage concurrency at the connection level, it handles it at the tenancy level since each DB connection is single-threaded. You could build up per-DB rate limiting on top of this pretty easily to prevent abuse by a given user.
Is there a straightforward way to set up Litestream to handle any arbitrary number of DBs?
Re: Bluesky migrates to single-tenant SQLite
#5I am curious, does the HN folks know if bluesky is more active than nostr or the mastodon network?
Less active than Mastodon, more active than nostr.
https://vqv.app/stats/chart is useful for Bluesky and draws on the Bluesky firehose for data. https://stats.nostr.band/ seems useful for nostr.
Re: Bluesky migrates to single-tenant SQLite
#6Interesting... I like the strategy of having each user be 1:1 with a DB. What would be done for data that needs to be aggregated across users though? If I'm subscribed to another user and they post, how does my DB get updated with that new post? Or is this meant just for durable data and not feed data (like profile data, which users are followed / not followed / etc.) and all the interactive stuff happens separately?…
Re: Bluesky migrates to single-tenant SQLite
#7This seems like a very misleading title, the Bluesky PDS is the meant-for-selfhosting thing they distribute, not the bluesky service as experienced and used by most of its users.
AFAIK there's only one version of the software so "the service" runs the same thing that you self-host. SQLite seems like it will simplify the single-user case though.
Re: Bluesky migrates to single-tenant SQLite
#8I am curious, does the HN folks know if bluesky is more active than nostr or the mastodon network?
Less active than Mastodon, I'd assume more active than Nostr.
But the interesting thing for me isn't activity — it's the people on there.
Of the cohort who had >100k followers on Twitter, I think more of them post regularly on Bluesky than post on Mastodon. Bluesky definitely has a more cohesive feel, especially because there's currently just one instance & mod team.
Re: Bluesky migrates to single-tenant SQLite
#9This seems like a very misleading title, the Bluesky PDS is the meant-for-selfhosting thing they distribute, not the bluesky service as experienced and used by most of its users.
no this actually is moving every single user currently on the service into this setup. Everyone gets their own sqlite under the hood.
Re: Bluesky migrates to single-tenant SQLite
#10I am curious, does the HN folks know if bluesky is more active than nostr or the mastodon network?
Bluesky is pretty positive and definitely lacks the "American Suburbia HOA" energy that some Mastodon instances have.
It's pretty active during North American hours.